Jira setup
Every organization uses Jira in a slightly different way. That's why we let you configure your Jira settings in a way that supports your teams current practices.
Last updated
Was this helpful?
Every organization uses Jira in a slightly different way. That's why we let you configure your Jira settings in a way that supports your teams current practices.
Last updated
Was this helpful?
First, confirm that all the necessary Jira Projects have been synced to Swarmia. These can be edited at any time by an admin. Once a project has been fully synced, a green check mark will appear.
Next, head to the 'General' tab and setup Issue Types in Swarmia. The purpose of this feature is to quickly communicate the size of work, and providing a filter that's compatible across Jira Projects to support teams with different processes and issue types they use in Jira.
The mapping might be as simple as an Epic in Jira is an Epic in Swarmia. But, if your organization is using any kind of customer issue type other than the four shown below, you will need to make sure it's mapped properly in order to view the data in Swarmia.
For example, if you have support tickets that you would like to track in Swarmia, try adding that Jira Issue Type to the 'Task' issue in Swarmia (or whatever makes the most sense for your team.) That work will then show in all 'Task' views in Swarmia and you can filter on those specific support tickets in the Flow Insights.
Swarmia models issue workflow based how much time issues spend in progress. We automatically set this up based on status type information from Jira to track this, but you might need to do some small tweaks (e.g. depending how you handle issues resolved as Won't Do).
Scroll down to Status mapping to review and make edits to how your statuses are mapped. Select which statuses coming from Jira need to be tracked as To Do, In Progress, Done, and Won't Do.
