Skip to main content
Version: Version 22

Jira application link

Introduction​

What is the Jira application link? The Jira application link is the foundation of the Jira Connectivity integration in Fortes Change Cloud. It establishes the secure connection between an FCC environment and a Jira instance, enabling two-way data exchange: FCC sends Portfolio items or program/project items to Jira, and Jira continuously feeds back the (updated) status of those items.

Who uses it?

  • Administrators and integration specialists who set up and maintain the Jira integration.
  • Portfolio and program managers who benefit from synchronized team data between Jira and FCC.

What value does it deliver?

  • A live, two-way connection so work items and statuses stay aligned between FCC and Jira.
  • Controlled authentication via OAuth 2.0.
  • The prerequisite for all further Jira Connectivity configuration, such as team configurations and field mappings.

Two-way synchronization: Items created in Jira from FCC keep their field mappings synchronized in both directions. When information is updated in FCC it is passed to Jira, and updates in Jira are fed back to FCC, so the link is continuous, not one-time.

Creating the link is a two-sided process: you register Fortes Change Cloud as an app in Jira, and then paste the resulting credentials back into FCC. The exact steps depend on whether you use Jira Cloud or Jira Data Center. FCC shows the values you need (such as the callback URL) on the application link page itself, with copy buttons.

Important: The Jira user you are logged in as while creating the link is the user FCC will act as. Make sure you are logged in to Jira as the intended API user before you start.

Jira Cloud (OAuth 2.0)​

Step 1: Register FCC in Jira

  1. Go to the Atlassian developer console: https://developer.atlassian.com/console/myapps/.
  2. Click Create and add a new OAuth 2.0 integration.
  3. Use the values shown by FCC on the application link page:
    • App name
    • OAuth 2.0 authorization callback URL
    • API scopes

Step 2: Copy the Jira data back into FCC

Paste the application information from the Jira page into the corresponding FCC fields:

  • Client ID
  • Client secret

Make sure the user currently logged in to Jira is the user FCC should use (the API user).

Jira Data Center​

For Jira Data Center the link is created as an application link in Jira, and you need ADMIN rights to do so.

Step 1: Register FCC in Jira

Register Fortes Change Cloud as a new application link using the values below. The user you sign up with in Jira also creates the application link.

  • Name: Fortes Change Cloud
  • Redirect URL: the callback URL shown by FCC (e.g. https://<your-environment>/jira/oauth2/callback)
  • Permission: ADMIN

Step 2: Copy the Jira data back into FCC

Paste the application link information from the Jira page into the corresponding FCC fields:

  • Client ID
  • Client secret
  • Jira URL: the link of the Jira instance.

Best practices​

  • Use a dedicated API user in Jira with the right permissions, rather than a personal account, so the link does not break when someone leaves.
  • Log in as that API user before creating the link. FCC acts as whoever is logged in to Jira at that moment.
  • Treat the Client secret as a credential: store it securely and rotate it if it may have been exposed.
  • Create the link once, reuse it in every team configuration; you do not need a separate link per team.

FAQ​

What is the difference between Jira Cloud and Jira Data Center setup? Jira Cloud uses an OAuth 2.0 integration registered in the Atlassian developer console; Jira Data Center uses an application link created in Jira itself, which requires ADMIN rights and also captures the Jira URL.

Which user does FCC act as? The Jira user that was logged in when the link was created. Use the intended API user.

Is the synchronization one-way or two-way? Two-way. FCC sends items and updates to Jira, and Jira feeds status updates back to FCC.

Do I need a separate link per team? No. One application link can be reused across multiple team configurations.

Need more support?​

For step-by-step instructions or troubleshooting, contact your Fortes Change Cloud administrator or consult in-app help.