Chapter 4. Creating and configuring a Jira connection


You can track application migrations by creating a Jira issue for each migration within the Migration Toolkit for Applications (MTA) user interface (UI).

4.1. Configuring Jira credentials

To define a Jira instance in MTA and establish a connection to that instance, you must first create an MTA credential to authenticate to the Jira instance’s API. You can create either of the following types of credentials:

  • For Jira Cloud and a private Jira server or data center, use the Basic auth credential type.
  • For Jira Cloud and a private Jira server or data center, use the Basic auth credential type. For a private Jira server or data center, use the Bearer Token credential type.
Important

You cannot delete a credential that has already been assigned to a Jira connection instance.

Procedure

  1. In Administration view, click Credentials.
  2. Click Create new.
  3. Enter the following information:

    • Name
    • Description (optional)
  4. In the Type list, select Basic Auth (Jira) or Bearer Token (Jira):

    • If you selected Basic Auth (Jira), complete the following steps:

      1. In the Email field, enter your email.
      2. In the Token field, depending on the specific Jira configuration, enter either your token generated on the Jira site or your Jira login password.

        Note

        To obtain a Jira token, you need to log in to the Jira site.

      3. Click Save.

        The new credential appears on the Credentials page.

    • If you selected Bearer Token (Jira), complete the following steps:

      1. In the Token field, enter your token generated on the Jira site.
      2. Click Save.

        The new credential appears on the Credentials page.

  5. Optional: To edit the credential, click Edit.

4.2. Creating a Jira connection

To track your application migrations, you can define a Jira instance in MTA and establish a connection to that instance.

Important

You cannot remove a Jira connection that you used for creating issues for a migration wave if the issues exist in Jira, even after the migration wave is deleted.

Prerequisites

Procedure

  1. In Administration view, under Issue Management, click Jira.
  2. Click Create new.
  3. In the New instance window, enter the following information:

    • Name of the instance
    • URL of the web interface of your Jira account
    • Select either the Jira Cloud or Jira Server/Data center instance type from the list
    • Select credentials from the list

      Note

      If you selected Jira Cloud as an instance type, only Basic Auth credentials are displayed in the list.

      If you selected Jira Server/Data center as an instance type, both Basic Auth and Token Bearer credentials are displayed.

      Choose the type that is appropriate for the particular configuration of your Jira server or data center.

  4. By default, a connection cannot be established with a server with an invalid certificate. To override this restriction, enable the Enable insecure communication switch.
  5. Click Create.

    The new connection instance appears on the Jira configuration page.

Verification

  • On the Jira configuration page, ensure that the connection has been established and authorized:

    • If the status of the Connection column displays Connected, the Jira connection is established and authorized.
    • If the status of the Connection column displays Not connected, click the status to check the reason for the error.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat