Contents:
How to access Jira integration settings
Open your story map
Go to "Settings"
Select "Integration settings"
Who can access or modify Jira integration settings
Only the Subscription Admin and the Story Map Admin can access the Jira integration or make changes. If you are a Member holding Editor rights on the story map and you may need to update the Jira integration settings, please contact the Admin of the story map.
Jira integration settings
General settings
When you link your story map to a Jira project you can manage how you would like to synchronize your data.
StoriesOnBoard supports real-time and bidirectional sync for the following:
sync title changes
sync description changes
sync estimation changes (additional settings required)
sync releases (additional settings required)
💡 Tip - Learn more about How to sync estimation field with story points in Jira
💡 Tip - Learn more about Release sync setup for Team managed project
💡 Tip - Learn more about Release sync setup for Company managed project
Disable synchronization
Use the disable/enable synchronization if you want to refresh the board
If you as an Admin of the story map wants to block the team from importing items
Use it if you want to refresh your status mapping settings
Disconnect Jira
In case you disconnect your story map from Jira items no longer will be synchronized between your story map and Jira project.
Once you need to connect your story map once again to a Jira project you will need to setup the integration again for the story map.
Using disconnect Jira will only unlink this particular story map from Jira
💡 Tip:
In case you link the story map once again to the same Jira project, all cards' link on the board will be reinstated.
Export settings
Select the issue type that should be created when new cards are sent to Jira. You can also enable/disable StoriesOnBoard card links to the JIra cards as attachment.
Variables
You can set additional Jira fields with predefined values when pushing cards into Jira. Variables are supported in labels. Labels are separated by spaces, commas, or semicolons.
💡 Tip - Learn more about How to add custom Jira fields to cards
Import settings
Select which issue types should be imported from Jira. During the import you can also ignore closed or done issues coming from Jira in order to avoid your story map becoming unnecessarily overloaded with issues.
It is also possible to visualize only a selected part of the Jira project on a story map by using JQL queries. This will allow you to only import those issues to the story map which is matching to your query.
💡 Tip - Learn more about How to import issues from Jira using JQL language
Furthermore, you can enable/disable for editor's ability to import new cards from Jira.
Status mapping
Setup status mapping between Jira and StoriesOnBoard to stay up-to-date at all time as issues are changing during execution. StoriesOnBoard identifies the workflow of your jira project and you can match Jira statuses with your statuses on the story map.
In case your Jira project has a custom workflow that requires additional status values to be created on the story map, you can create your custom workflow on StoriesOnBoard as well.
⚠️ IMPORTANT ⚠️
Please note once you established the connection between StoriesOnBoard and Jira, card statuses will be only editable from Jira. This is a built in security to allow teams to execute the project without any interruption. To modify the status of linked cards visit open the cards in Jira and update its status. Thanks to the status mapping, that will be applied automatically on the story map as well according to your settings.
💡 Tip - Learn more about How to setup your custom workflow on StoriesOnBoard.
Jira issue keys on cards
When a card is connected to Jira, the Jira issue key is displayed on the card on the story map as well. This allows you to easily find or identify issues on the story map without even opening each cards on the board.
