JIRA Integration

Transfer your structured requirements to JIRA with a single click while maintaining complete traceability and context.

Key Features

• One-Click Export: Transfer entire requirement sets to JIRA instantly
• Complete Context: Preserve all relationships and background information
• Full Traceability: Maintain links between requirements and original content
• Rich Content Transfer: Include all associated information:
  • Original requirements context
  • Mockups and screenshots
  • Effort estimates
  • Acceptance criteria
  • Related entities, stories, tasks and epics

Configure Jira Connection

• Configure Jira Connection in the connections page
• Add your Jira host, your user and your Jira token

Note: this will be the user that will be used to create the issues in Jira.

• Click on “Save and test”
• You will get feedback on whether the connection was successful or not.

Connection possibilities

Direct Connection

With the token set and a jira host reachable from storywise, you can directly connect to Jira. If you use a self-hosted Jira, you need to make sure that the host is reachable from storywise (contact us if you need help with this). In the top menu in a project, you will find a “Sync” button. Clicking it will bring you to the project connection page, if you have not connected your project yet. If your project is already connected, you will be able to choose which content you want to sync to Jira.

Sync Mode: You’ll be able to choose between:

• Only new content: Only synchronizes epics/stories/tasks that have been created since the last synchronization to Jira.
• New content and update existing: Synchronizes new epics/stories/tasks created since the last sync and updates content of existing items - like descriptions, acceptance criteria, screens and links.
• Delete and resync all: Deletes all previously synchronized stories and transfers them again completely.

Note: If you choose to delete and resync all, storywise will still only delete and recreate stories that were created in storywise.

Note 2: If you have deleted stories in Jira, you need to do a manual deletion in storywise to delete them.

Epic Options:

Now you can choose which epics you want to sync to Jira.

Features and Releases:

You can choose for each feature and release if you want to sync it to Jira. This is the same status as in the pricing and export page. storywise will remember the last choice, if saved, so you get the same result as in the pricing and export page. However, you can override the status without saving the choice if you want to, for example if you want to export a feature without syncing it to Jira. storywise will also remember who saved the choice.

Safety questions:

You will be asked to confirm the sync if you are choosing to delete and resync all and see the list of epics that will be deleted and recreated.

Export CSV

You can export the current content to a CSV file. This can be useful if you want to use the content in a Jira instance that is not reachable from storywise, e.g. a self-hosted Jira.

How to import your CSV file into Jira:

1. Download our configuration file: Download
2. In Jira, navigate to: System Settings → External System Import → CSV, select the exported CSV file
   • Select “Use an existing configuration”, use the CSV-Jira-Import-Config.txt (from step 1)
   • Then, click → Next
3. Select the project and click → Next
4. For field selection click directly → Next (all CSV fields should have an assigned Jira field)
5. Start import

There are different versions of the CSV-Jira-Import-Config.txt file, depending on your instance and configuration of jira. If you need help setting up the import, please contact us.

How to get a JIRA API token

Follow these steps to create your API token:

1. Log in to your Atlassian account and go to: https://id.atlassian.com/manage-profile/security/api-tokens
2. Click on “Create API token”
3. Copy the created token and paste it into storywise

Note: This is the only opportunity to copy the token. If you lose the token, you will need to create a new one.