Effective 7 September 2026. These terms apply to Mercury Cloud, operated by NWGG Pty Ltd. They do not replace the separate terms that apply to Mercury Server.
Using Mercury
You must have authority to install the app for the relevant Jira site and to accept these terms for your organization. Use Mercury only with Jira sites, projects, issues, and data that you are authorized to access.
Atlassian's terms govern Jira, Forge, Marketplace distribution, and the Atlassian platform. Your use of Mercury also depends on those services.
Scripts and administrator responsibility
Your organization controls its scripts, configuration, issue selection, and enabled automations. Jira administrators must review source, permissions, proposed writes, pinned revisions, execution limits, and project filters before enabling live execution.
Simulation and dry run help with review but do not prove that a later live Jira request will succeed. Completed Jira writes cannot be rolled back by Mercury. Automatic execution is not exactly once, and Mercury does not automatically replay a failed run.
Execution controls
Mercury applies source, runtime, Jira-call, automation-count, and installation usage limits. The server admits no more than 100 runs per UTC hour or 10,000 per UTC month for one installation, and an administrator can lower those limits. These counters are operational controls rather than a spending or billing meter. An administrator can pause new execution. Pause does not cancel a run that has already started. Mercury may reject or suspend execution when a license is inactive, a limit is reached, or continued execution could threaten the app or Atlassian services.
Your content
Your organization retains its rights in scripts and configuration it provides. You grant the permission needed for Mercury and Atlassian Forge to store and process that content to provide the app. Do not place credentials, private keys, or unnecessary sensitive data in source or logs.
Mercury software
Mercury Cloud software and documentation are copyright 2026 Johnathan Crawford. Except for rights provided by an applicable Marketplace order or separate written agreement, no rights are granted to copy, modify, distribute, sublicense, or sell the software.
Service changes and availability
Features can change as Jira and Forge change. Mercury does not promise uninterrupted or error-free operation. Scheduled execution depends on Forge trigger delivery, and Jira responses depend on site configuration, permissions, workflows, and Atlassian service availability.
Warranty and liability
To the extent permitted by law, Mercury is provided as is and without implied warranties. Nothing in these terms excludes a right or liability that cannot legally be excluded. Any commercial order or separate written agreement can provide additional terms that take priority where they conflict with this page.
Ending use
You can stop using Mercury by disabling its automations and uninstalling the app. Forge hosted data follows Atlassian's uninstall lifecycle, described on the data retention page.
Questions
Use the channels on the support page, or email plugin-support@johno.it for a private question. Do not post confidential information in a public issue.