Roadmapping data can often be found in development tools. Roadmunk enables that data by giving it the proper visibility and exposure to the organization.
Roadmunk's JIRA integration allows users to
- Import up to 300 JIRA issues and related meta-data per roadmap
- Map JIRA fields to Roadmunk fields
- Use an existing JIRA login. It is strongly recommended to use an administrative account to avoid permissions problems
- Full support for Cloud JIRA (also branded as JIRA on Demand)
- Support for Hosted JIRA as per requirements below
Hosted JIRA Requirements
- JIRA Server should publicly accessible so the Roadmunk server can connect
- JIRA version is relatively new (the bulk of the integration code has been written against JIRA 6.3.15)
- If the server is hidden by a VPN or corporate network then Roadmunk's IP address must be whitelisted to allow for JIRA / Roadmunk communication
- If the ports from JIRA are forwarded to the internet, ensure that the URL entered is correct
- All intermediate certificates need to be valid
JIRA Data (Getting Started)
On the table view and select Import and then Import from JIRA
Enter login information to a JIRA account.
Important: JIRA usernames are NOT usually an email address. Verify the correct JIRA username.
Use the filters to narrow down which JIRA issues to import.
Key points to remember
- Importing multiple projects into one roadmap is possible
- Import only the issues types that need to be roadmapped (Bugs are not useful to roadmap)
- Roadmunk will find all status types across all projects and issue types -- being aware of which statuses are used in which project is important
Roadmunk automatically maps the four default fields from JIRA -- if they exist.
Choose additional JIRA fields and data to import by selecting + Add New Mapping.
Make sure to line up fields types correctly. Roadmunk will automatically detect some types, but best practice is to check to be sure.
Use the drowdown menu to select different fields from JIRA.
JIRA Data on the Table View
There are two key differences in the table view when integrating with JIRA.
- The ExternalID field is taken from JIRA and the Roadmunk assigned IDs are not used
- There is a green / yellow / red indicator which signals when the JIRA data is out of sync
- Green indicates that the issue matches the JIRA filterset
- Yellow indicates that the issue has been modified in JIRA but still matches the filterset
- Red indicates that the issue no longer matches the filterset
Re-sync with JIRA
To update data from JIRA click on the JIRA button on the table view once a JIRA sync has been set up. Roadmunk will go to the final step and provide two options for performing a re-sync.
There are two possible workflows when using Roadmunk with JIRA.
Roadmunk as a Visualising Tool
In this workflow resources and data are all managed by JIRA, and Roadmunk is used purely for visualising the issues in JIRA. When using this workflow, the Sync & Overwrite All option should be selected.
Roadmunk as a Planning Tool
In this workflow, some planning and changes are done in Roadmunk which should not be overwritten with older JIRA data. When using this workflow, the Import New Issues Only option should be selected.