Every time when you create a smart variable - it is created as String, not as a number.Edit issue: Do not choose fields but set Additional fields.Issue field condition: Issue type is one of Incident, Problem.When: Field value changed for Impact, Urgency during Create issue/ Edit issue.The whole automation to calculate the priority consists of a trigger, issue scope and 5 components: Where NumberOfColumns represents the number of Urgency values, in our case we have 4. To get the "address" of the priority we need to use the following formula: (Impact+Urgency) + ((Impact-1) * (NumberOfColumns-1)) - 2 1st element (i1/u2): 1 - Critical again.0th element corresponds to (i1/u1) with the value of 1 - Critical.The numbers in the coloured cells are sequential and serve a purpose to "address" the priority value in the list of priorities which can be defined as a priority sequence: 1,1,2,3,1,2,3,4,1,2,3,4,2,3,4,4 It is possible you might have other priorities like 5, and 6 - but it does not matter, since the approach will work for any number of. The priority value is shown by colour, where red - priority is 1, orange - 2, yellow - 3, and green - 4. Jira stores priorities in a format of id/name pairs.įor simplicity, I will be referring to the priorities in this post by numbers, whereĪ similar approach applies to two custom fields we have created for urgency and impact, where these fields can be either of these valuesĪs you can see - impacts and urgencies values are prefixed by a number which makes it easier to operate within the automation later.īelow is the sample matrix of impact and urgency resulting in the priority. We have come up with an approach where only 5 components are required to derive the priority of the "unlimited number" of impact/urgency combinations. And you will need to create a number of these automations to finish this task. There is always a way to create a long-running set of if-else conditions in the automation, however, depending on the complexities in your impact/urgency definitions, this set can be really long (hard to maintain) and can exceed the maximum allowed number of components in the automation. (Datetime and datepickers are among the custom fields)Ĭom.customfieldtypes:labelsĬom.customfieldtypes:radiobuttonsĬom.customfieldtypes:selectĬom.customfieldtypes:multicheckboxesĬom.customfieldtypes:multiselectĬom.customfieldtypes:textareaĬom.customfieldtypes:textfieldĬom.customfieldtypes:datetimeĬom.customfieldtypes:datepickerĬom.customfieldtypes:floatĬom.customfieldtypes:urlĬom.:gh-epic-link (Jira Software - Sprint)Ĭom.atlassian.teams:rm-teams-custom-field-team (Portfolio - Team)Ĭom.:tests-associated-with-test-plan-custom-fieldĬom.:test-plans-associated-with-test-custom-fieldĬom.:test-sets-custom-fieldĬom.:test-plan-custom-fieldĬom.:test-set-status-custom-fieldĬom.:test-plan-status-custom-fieldĬom.:test-execution-status-custom-fieldĬom.:test-run-status-custom-fieldĬom. company has recently had a case when we needed to derive a priority using a rather complex Impact / Urgency matrix. Project (name and key)descriptionsummarysubtasksissuelinksStories in Epic List of supported Jira fields in the traceability matrix We may not have all Jira fields, but we've already developed renderers for Xray fields ( Xray integration with Requirement Yogi) and we could do it for you too. It can't be used to display % coverage, for example. You can't display the percentage of children in a given status, for example. The user can empty his cached data by using the checkbox next to the "Get data from Jira" existing checkbox. Jira integration is now faster since you can benefit from a cache.Īs a user, the data you are seeing in the matrix is kept during 5 days. This matrix can really gather a lot of information, and we recommend using it a lot. Of course, each Jira field can be displayed in the matrix in Confluence:Īll of these options are available using the cog menu:Īnd if you Jira issues are linked to Jira issues: If you have requirements attached to Jira issue, they can be included:
0 Comments
Leave a Reply. |