Terms of Use for the Nanga Jira Codebeamer Connector

Last updated: 29 October 2026

§ 1 Provider and scope

1.1 These Terms of Use ("Terms") govern the use of the Nanga Jira Codebeamer Connector ("NJCC") provided by:

NANGA SYSTEMS GmbH
Königstraße 27
70173 Stuttgart
Germany

Registered at Amtsgericht Stuttgart, HRB 750 626. VAT ID DE297537569.
Email: info@nangasystems.com. Phone: +49 800 800 1007.

("Nanga", "we", "us").

1.2 NJCC consists of the following components, each of which is part of the "Software":

• The agent: a server application, delivered as a Docker image or as a standalone JAR file, that the customer runs on its own infrastructure. It synchronizes work items between Jira and Codebeamer and, through its OSLC connector, links Jira issues to Codebeamer items.
• The Codebeamer plugin: an extension installed in the customer's Codebeamer server.
• The Jira Forge app: an app for Jira Cloud, distributed through the Atlassian Marketplace, that shows sync status, sync errors and linked Codebeamer items in Jira.
• The documentation, updates and any other material we provide for NJCC.

1.3 NJCC is offered to businesses, public bodies and other professional users only. It is not offered to consumers within the meaning of § 13 BGB. If you and Nanga have signed an order, a quote or a separate license agreement for NJCC (the "Order"), the Order takes precedence over these Terms where they differ. In all other respects these Terms apply. Terms and conditions of the customer do not apply, even if Nanga does not object to them.

1.4 "Customer" or "you" means the organization that installs or uses the Software. "Users" means the people the Customer allows to use the Software, including Jira and Codebeamer users who see or use its features.

§ 2 What NJCC does and what it does not do

2.1 NJCC connects Atlassian Jira and PTC Codebeamer. It copies and updates work items, fields, comments, attachments and links between the two systems according to the configuration the Customer sets, and it lets Users link Jira issues to Codebeamer items.

2.2 Nanga does not provide Jira, Codebeamer, hosting for either system, or user accounts in either system. The Customer operates Jira and Codebeamer itself or has a provider of its choice operate them, for example Atlassian, PTC or a hosting partner. The Customer needs its own valid licenses for Jira and Codebeamer and must comply with the terms of Atlassian and PTC.

2.3 Nanga does not host the agent and does not receive the data it processes. The agent, its database and the data it syncs and links stay on infrastructure the Customer chooses and controls.

2.4 Jira and Atlassian are trademarks of Atlassian Pty Ltd. Codebeamer and PTC are trademarks of PTC Inc. NJCC is not a product of Atlassian or PTC and is not endorsed by them.

§ 3 License

3.1 Subject to these Terms and to payment of the fees agreed in the Order, Nanga grants the Customer a non-exclusive, non-transferable, non-sublicensable right to install and use the Software for its own internal business purposes for the term stated in the Order or in the license key.

3.2 Each license key is issued for one Jira site and one Codebeamer server, identified by their URLs. Using the Software with other sites or servers requires a separate license key. Test and staging systems require their own license key unless the Order says otherwise.

3.3 Evaluation and trial licenses are valid for the period stated in the license key, may only be used to evaluate the Software, and are provided without any warranty beyond what § 11.1 requires.

3.4 The Jira Forge app is free of charge. It only works together with an agent that holds a valid NJCC license. The license for the Forge app ends automatically when the Customer's agent license ends.

3.5 All rights in the Software not expressly granted remain with Nanga and its licensors. The Software contains open source components, which are licensed under their own licenses. The list of these components and their licenses is part of the delivery. Nothing in these Terms limits the rights the Customer has under those licenses.

§ 4 Fees and payment

4.1 Fees, payment terms and the license term are set out in the Order. Unless the Order says otherwise, fees are due within 30 days of the invoice date and are exclusive of VAT.

4.2 The Jira Forge app is listed free of charge on the Atlassian Marketplace. Atlassian does not invoice the Customer for NJCC, and Atlassian's refund policies do not apply to NJCC licenses.

§ 5 Acceptable use

The Customer must not, and must ensure that its Users do not:

1. Copy, modify, translate, decompile or reverse engineer the Software, except where §§ 69d and 69e UrhG (German Copyright Act) expressly allow it.
2. Remove, bypass or tamper with the license key check, or use the Software beyond the sites, servers or term of the license.
3. Rent, sell, sublicense or provide the Software to third parties, or run it as a service for third parties, unless the Order allows it.
4. Use the Software to get around permissions in Jira or Codebeamer, for example to give Users access to items they could not see otherwise.
5. Use the Software to attack, overload or probe the systems of Atlassian, PTC, Nanga or anyone else, or to send malicious code.
6. Use the Software in breach of applicable law, the rights of third parties, or the terms of Atlassian or PTC.
7. Remove copyright notices or trademarks from the Software or the documentation.

Nanga may suspend support or terminate the license under § 13.3 if the Customer seriously breaches this section.

§ 6 Customer responsibilities

6.1 The Customer is responsible for:

1. Installing, operating, securing and updating the agent and its database, including TLS certificates, the reverse proxy and network access.
2. The sync configuration, in particular which projects, trackers and fields are synced and in which direction, and the projects for which linking is enabled.
3. Testing the configuration on a test system before it is used in production.
4. Regular backups of Jira, Codebeamer and the agent database. Nanga cannot restore data in the Customer's systems.
5. Keeping the credentials, API tokens and license key used by the agent secret, and giving the agent only the permissions it needs. This includes the key that encrypts the OSLC connector's signing key, because the agent uses it to call Codebeamer as the signed-in user.
6. Having a legal basis for any personal data it processes with the Software, for example names, email addresses and account IDs of Jira and Codebeamer users.

6.2 Bidirectional sync writes to both systems. A wrong configuration can change or overwrite data in Jira and Codebeamer at the same time. The Customer must check the result of every configuration change before enabling it for production projects. Linking does not change existing data. It acts as the signed-in user, with that user's permissions in Jira and Codebeamer.

§ 7 Regulated use

The Customer may use NJCC in regulated environments, for example under ISO 26262, IEC 62304, ISO 13485, DO-178C or 21 CFR Part 11. Nanga does not warrant that NJCC on its own meets the requirements of any regulation or standard. The Customer is responsible for validating NJCC for its intended use, including its configuration, and for keeping the records its regulations require. Nanga will provide reasonable information to support the Customer's validation on request.

§ 8 Data

8.1 The Customer remains the owner of all data in its Jira and Codebeamer systems and in the agent database ("Customer Data").

8.2 The agent runs on the Customer's infrastructure. The license key is checked locally and the agent does not send Customer Data, usage data or telemetry to Nanga.

8.3 Nanga only receives Customer Data when the Customer sends it, for example log files or screenshots in a support request. Nanga uses that data only to provide support and deletes it when the request is closed, unless the law requires longer retention. Where this involves personal data, Nanga processes it as a processor and the Customer may request a data processing agreement under Art. 28 GDPR.

8.4 How Nanga handles personal data is described in the privacy policy at https://nangasystems.com/njcc-pp.

§ 9 Jira Forge app and the Atlassian Marketplace

9.1 Relationship with Atlassian. The Forge app is provided by Nanga, not by Atlassian. Atlassian is not a party to these Terms and is not responsible for the Forge app, its support or the data it processes. Use of Jira Cloud and the Atlassian Marketplace is governed by Atlassian's own terms.

9.2 How the app works. The Forge app runs on Atlassian's Forge platform. It does not store Customer Data outside Atlassian itself. It forwards requests from Jira to the agent address a Jira administrator enters in the app settings. Every request is signed by Atlassian with a Forge Invocation Token, and the agent accepts requests only from the Jira site its license and configuration allow. The app is not eligible for the "Runs on Atlassian" badge, because it exchanges data with the Customer's agent.

9.3 Data stored by the app. In Atlassian's Forge storage the app keeps its settings: the agent address, the enabled projects, and the Jira groups that may see sync details or retry failed syncs. It also sets project properties in Jira that control where its panels appear. Atlassian deletes the app's Forge storage under its own policies when the app is uninstalled. Data in the agent stays on the Customer's infrastructure and is deleted by the Customer.

9.4 Platform quotas and rate limits. The Forge app is subject to the quotas and limits Atlassian sets for Forge apps, including limits on function invocations, runtime, memory, storage and requests to external services. Jira Cloud also limits the number of API calls the agent may make. When a limit is reached:

• The sync status panel, the sync errors page or the Codebeamer link dialog may load slowly, show an error, or not load until the limit resets.
• The agent waits and retries the affected syncs. Changes are then synced with a delay. Syncs that still fail are listed on the sync errors page, where they can be retried.

Nanga has no control over these limits and is not responsible for interruptions they cause. Atlassian's current limits are published in the Forge documentation.

9.5 Availability. The Forge app depends on the availability of Jira Cloud, the Forge platform and the Customer's agent. Nanga does not guarantee that any of them is available at any time.

9.6 Marketplace links. The Atlassian Marketplace listing links to these Terms, the privacy policy, the documentation and the support contact in § 12.

§ 10 Warranty

10.1 Nanga warrants that the Software substantially works as described in the documentation for the version delivered, when used with the system requirements stated there.

10.2 The Customer must report defects in text form without undue delay, with a description that allows Nanga to reproduce them. Nanga will remedy reported defects within a reasonable time, at its choice by a fix, an update, a workaround or a new version. If the remedy fails, the Customer's statutory rights to reduce the fee or terminate apply. Claims for damages are governed by § 11.

10.3 For licenses granted for a term, strict liability for defects that already existed when the Software was provided (§ 536a (1), first alternative, BGB) is excluded.

10.4 There is no warranty for defects caused by: use outside the system requirements, changes to Jira, Codebeamer or the Forge platform made by Atlassian, PTC or the Customer after the version was released, a configuration the Customer chose, or modifications not made by Nanga.

10.5 The warranty period is 12 months from delivery of the respective version, except for claims under § 11.1.

§ 11 Liability

11.1 Nanga is liable without limitation for intent and gross negligence, for injury to life, body or health, under the German Product Liability Act (Produkthaftungsgesetz), and where Nanga has given a guarantee.

11.2 For slight negligence, Nanga is liable only for breach of an essential contractual obligation. An essential contractual obligation is one whose fulfilment makes the proper performance of the contract possible in the first place and on which the Customer may regularly rely. In that case liability is limited to the damage that is typical and foreseeable when the contract was made.

11.3 Liability for slight negligence is otherwise excluded.

11.4 If data is lost, Nanga is only liable for the effort needed to restore it from backups the Customer should have made under § 6.1.

11.5 The limits above also apply to the personal liability of Nanga's employees, representatives and agents.

11.6 For the free Forge app, Nanga is liable in the same way as for the agent, because the app is part of the licensed product.

§ 12 Support and security

12.1 Support is provided in English and German by email to support@nangasystems.com on German business days between 9:00 and 17:00 CET. Nanga responds to support requests within 5 business days. Critical issues are answered within 24 hours. The Order may agree a different support level.

12.2 Nanga provides updates for NJCC, including updates that keep it working with new versions of Jira, Codebeamer and the Forge platform, during the license term. Nanga supports the latest released version. The Customer must install updates within a reasonable time to keep warranty and support.

12.3 Security vulnerabilities must be reported to security@nangasystems.com. Nanga handles them under its published security policy and informs affected Customers directly about critical and high vulnerabilities.

12.4 If Nanga becomes aware of a security incident in the Software that affects Customer Data, it will inform the affected Customers without undue delay.

§ 13 Term and termination

13.1 The license starts when the Customer receives the license key and runs for the term stated in the Order or in the license key. Licenses for a term renew only if the Order says so.

13.2 The Customer can stop using the Forge app at any time by uninstalling it from Jira. This does not end the agent license or the duty to pay fees under the Order.

13.3 Either party may terminate for good cause without notice. Good cause for Nanga includes a serious breach of § 5, or the Customer not paying fees that are more than 30 days overdue despite a reminder.

13.4 When the license ends, the Customer must stop using the Software and delete the license key. The agent stops syncing and linking when the license key expires. Customer Data stays in the Customer's systems and is not affected.

13.5 Nanga may discontinue NJCC or a component of it, including the Forge app, with at least six months' notice. Licenses already paid for remain valid until the end of their term. Nanga will continue to provide security fixes until then.

§ 14 Confidentiality

Each party will keep the other party's confidential information secret and use it only to perform the contract. This includes license keys, pricing in the Order, and any Customer Data Nanga receives in support. This obligation continues for three years after the contract ends.

§ 15 Export control

The Customer must comply with applicable export control and sanctions laws of the European Union, Germany and the United States when using the Software. The Customer must not use the Software in, or provide it to, a country, organization or person that is subject to such restrictions.

§ 16 Final provisions

16.1 These Terms are governed by the law of the Federal Republic of Germany. The UN Convention on Contracts for the International Sale of Goods (CISG) does not apply.

16.2 Nanga may change these Terms for future license terms. Nanga informs Customers of changes in text form at least six weeks before they take effect. If the Customer does not object before that date, the changes are deemed accepted. Nanga will point out this consequence in the notice. If the Customer objects, the previous Terms continue to apply until the end of the current license term.

16.3 The exclusive place of jurisdiction for all disputes arising from or in connection with these Terms is Stuttgart, Germany. Nanga may also sue the Customer at its general place of jurisdiction.

16.4 Before going to court, the parties will try to resolve a dispute by negotiation between their responsible managers for at least 30 days.

16.5 Amendments and side agreements must be in text form.

16.6 If a provision of these Terms is invalid, the remaining provisions stay valid. The statutory provision replaces the invalid one.