Can I integrate more than one Jira project?
No, you can only integrate one Jira project per roadmap. This applies even if you try to use JQL to pull in multiple projects. However, the solution to this is to integrate each project into separate roadmaps then create a Master Roadmap that rolls up each of the project roadmaps. You can read more on Master Roadmaps here.
What's the value of JQL?
With JQL, you can write your own query. This means being very specific with the data you're pulling from Jira.
Basic = Bugs, Stories and Tasks with Open, Closed or Backlog status. This means you'll sync all items associated even if you don't need them. You can of course filter out issues within Roadmunk once imported.
JQL = Open Bugs assigned to Mike from January 1, 2018 to January 1, 2019. With this example you can get as precise as you need outside of just standard Issue Types and Statuses.
If you're interested, you can read more about JQL and building your own query using the links provided.
Do you offer Real Time syncing?
You can manually Sync at any time to push/pull changes to your roadmap, or set your sync to every hour.
If your sync is set to run every hour, the last change to occur prior to the sync running will be prioritized. If you want to make an update that updates both systems immediately - make the change then select Synchronize Now.
Why are my updates being written over? How can I avoid this from happening?
If you have a two-way sync set up and someone is making changes in Jira while your roadmapping, Jira always wins. Don’t wait for the scheduled sync. You should always manually push and sync your roadmap while making changes. Think of saving a document as you go - it’s good practice to not lose your work in a worst-case scenario.
Additionally if changes have occurred on both systems within your sync schedule, the most recent update occurs. For example, if a link item has been changed in this order, Roadmunk, Jira, Roadmunk, then you can expect the Roadmunk change to be prioritized.
Why can’t I update some fields like for Jira in Roadmunk?
The more complex and automated a field is, the more likely it can only be integrated as read-only. Read-only and mandatory fields will be greyed out. Fields already checked will be mandatory and can't be removed. You can see a full list of all the fields we support and how they come through the Roadmunk integration here.
Why isn’t the field I want showing up on the fields to sync screen?
Either the field is not on the Create Issues screen in your Jira project or it isn’t supported at this time.
Why am I seeing field values from another project?
Most Jira fields are treated like account-level fields in Roadmunk. Because of this, their values are shown within most synced Jira fields. For example, you may see more than one “Epic” field under your Issue Types. The big payoff is that you can use them as common pivots on a Master Roadmap (Issue Type, Epic link, Component, Label, Assignee).
Why am I getting an error when I try to push an item to Jira?
You'll want to ensure you're selecting the correct field. For example, Issue Type is similar to an Account Level field and it contains issue types from all integrated projects on their Jira server. Since there are some standard-issue types (Epic, Story, Task) they may appear multiple times. Selecting the correct one will get your item pushed to Jira.
I've synced my project with Roadmunk. What can I do now?
Now that your data is in Roadmunk, you can start building your visualizations. Roadmunk allows you to build informative views using both your fields created in Roadmunk and those brought in from Jira. If you're looking for ideas to get started, you can view our article on Jira specific views here (add views link)
Why is Roadmunk forcing a filter on me? How do I get around this?
Roadmunk has a default header capacity of 25 values. This helps with the general performance while using the tool. As Jira fields work similar to Roadmunk Account Fields, you're likely to see a lot. If you're looking to increase your header range, please reach out to our Support team.
Why can't I connect to my hosted Jira Server?
Here are a few examples of why some On-Prem solutions may have difficulty connecting to Roadmunk:
1. Your server may not have valid SSL/TLS certificates - test the URL here
2. Your company may be blocking outside access to your Jira server, you may need to whitelist Roadmunk's IP addresses to allow access. You can find more information here
3. Your Jira server may not be hosted at the root of the URL. For example: https://jira.mycompany.com will work, but https://mycompany.com/jira will not work
4. If you are still unable to connect to your Jira server and have verified the above does not apply, please ask your IT department to look for Roadmunk's ip addresses (see link above) in your network logs and try to determine why access may be getting blocked.
I’m getting a “Failed to Connect” error. What does this mean?
Roadmunk will timeout if it takes more than 10 minutes to sync your Roadmap. Timeouts can be remedied by manually tasking your Roadmap to sync again. Rule of thumb, if you’re bringing in more than 1000 items or a field with 150+ values, try adjusting your settings to bring in a smaller item count.
My integration has an error code but there's no additional messaging. What should I do?
Jira error messages generate codes for a variety of reasons. If you do receive a code without an associated message, please reach out to our support team with your specific code for further troubleshooting steps.