Version Select for Jira — Terms of Use
Draft for publisher review. Not yet effective. Before publication, complete the publisher details, effective date, governing law and liability provisions below and reconcile them with the Marketplace offer and any negotiated customer agreement.
Publisher: [PUBLISHER LEGAL NAME AND ADDRESS]
Support and legal contact: support@fogsea.top
Effective date: [DATE]
1. Agreement and authority
These Terms govern the customer's use of VersionSelect for Jira (the App), provided by the Publisher. By installing or using the App after these Terms are made available, you agree to them on behalf of yourself or the organization you are authorized to represent. If you lack that authority or do not agree, do not install or use the App. Atlassian's terms separately govern Jira, its Marketplace and platform services.
2. Permission to use
Subject to these Terms and the applicable order, the Publisher grants the customer a non-exclusive right to use the App for its internal business purposes during the authorized subscription or availability period. The Marketplace listing or order specifies any fees, evaluation period, user limits, renewal and cancellation conditions. These Terms do not create a charge absent an applicable offer accepted by the customer. Applicable open-source component licenses continue to govern those components.
3. Customer responsibilities
The customer manages its Jira permissions, users, catalog content and external API. It must have the rights and lawful basis needed for information it supplies and for the processing it instructs. The customer must protect catalog credentials and use the App lawfully. It must not use the App to obtain unauthorized access, distribute malicious code, interfere with other customers or violate third-party rights. Statutory rights that cannot be restricted remain unaffected.
Do not enter personal or sensitive information in service names, groups, versions or search text. Catalog choices are shared across the installation; groups are descriptive and do not impose project-level access controls.
4. Functionality and dependencies
Customer administrators can create, view, edit, delete and reorder services and versions on the manual data-source configuration page, or maintain the active API catalog in their own backend service. Removing an active catalog entry does not automatically erase old manual-catalog records or Jira field values. Those records follow their separate retention and deletion processes.
The App records service/version selections on Jira work items using a manual catalog or an administrator-selected API implementing the documented contract. A recorded selection is not proof of a deployment, release approval or software availability. The App depends on Jira, Forge and, in API mode, the selected catalog service. The customer is responsible for that service's availability, permissions and terms.
Existing work item values retain name and identifier snapshots. Removing or renaming catalog entries does not rewrite them, but removed options are no longer available in picker search. Maximum entries below 20 apply to the App picker; Jira enforces the documented hard limit. See the user documentation for scope and limitations.
5. Customer data and privacy
The customer retains its rights in customer data. It authorizes the Publisher and necessary service providers to process that data only to provide and support the App, follow lawful customer instructions and meet legal obligations, as described in the Privacy Policy. An executed data processing agreement governs personal data processing where applicable and prevails over these Terms on that subject.
API mode sends the catalog credential and lookup parameters to the customer-selected API. The Publisher does not view customer logs online or download them; customers manage their own log downloads. The Privacy Policy describes retention and processing locations. The App does not promise that all processing remains in a single region.
6. Support and changes
Support is available through the published support contact. No particular uptime, response time or resolution time is guaranteed unless separately agreed in writing. The Publisher may maintain or update the App and documentation. Material changes to these Terms will be published with a new effective date and reasonable notice where practicable; changes will not retroactively alter an accepted order contrary to applicable law.
7. Suspension and termination
The customer may stop using and uninstall the App and cancel any subscription through the applicable purchasing channel. The Publisher may suspend access where reasonably necessary to address unlawful use, a material breach or an immediate security risk, using proportionate measures and notice where practicable. For remediable breaches, the Publisher will provide a reasonable opportunity to remedy before termination unless immediate action is legally required or necessary to protect the service.
Termination does not immediately erase all data. Forge hosted data follows the platform lifecycle; Jira values, customer exports, external catalog records and support records have separate handling. The customer may request deletion through the deletion process. Mandatory legal retention and enforceable data protection obligations remain applicable.
8. Warranties and responsibility
To the extent permitted by applicable law and except as expressly agreed, the App is provided as available without a promise of uninterrupted or error-free operation or suitability for a particular purpose. No provision excludes mandatory warranties, remedies or liability that cannot lawfully be excluded.
Publisher decision required before publication: specify a proportionate aggregate liability cap, its measurement period and treatment of free use, excluded loss categories, and exceptions for fraud, deliberate misconduct, confidentiality, data protection and other mandatory liabilities. No numerical cap has been assumed in this draft.
9. Governing law and general terms
[GOVERNING LAW AND DISPUTE FORUM — PUBLISHER TO CONFIRM], subject to mandatory jurisdiction and consumer protections. If a provision is unenforceable, the remaining provisions continue to apply to the extent permitted by law. A negotiated customer agreement controls over conflicting standard terms where it expressly says so.
Questions and notices should be sent to support@fogsea.top.