Skip to main content

Jira Software Data Source

Txture allows to natively connect to a Jira instance (both on-prem or in the cloud). One use case for this is tracking progress during a migration by annotating an issue ID on the assets in Txture (or, alternatively, by tagging the Jira issue with a Txture ID). However, given the versatility of both Jira and Txture a range of use cases apply.

Connection configuration​

The integration requires the following configuration:

  • Instance URL - The URL of your Jira instance
  • Username - Your Jira username
  • Password / API Token - Either a password or an API token
  • Custom HTTP headers (optional) - Additional headers sent with all requests (helpful if you operate Jira behind a proxy such as an API gateway)

Importer configuration​

Jira Software can natively be queried from Txture in order to import issues as assets or augment existing assets in Txture with information from Jira. A typical example is tracking the state of an issue that contains migration steps. This allows to feed the current status back to Txture and track the migration progress.

Let's assume there is a Jira issue for each application to be migrated. Each of these Jira issues has a field with the corresponding Txture ID of the asset. This will allow to match the Jira issue with the assets in Txture.

After creating a Jira data source, the next step is to create a property importer (as the goal is to import property values to existing assets):

The next Jira-specific step is to select a JQL query (Jira Query Language) that yields the results required. In the example all issues of a project are selected that are currently in the "In QA" status.

Atlassian offers an excellent JQL cheat sheet that might be helpful in formulating the queries.