Hi Jira Community -
I need to setup an automation to create a weekly release based on the name of the Active Sprint. (In the past I created releases with names based on the date the autom, ran).
However our project has 2 diff boards and 2 diff sprint names conventions, I am interested in getting the Sprint Name from one board. I can set the Board ID in a Lookup Table step in my automation.
So the question really is, how to pull the Sprint Name associated to a given board id.
Thanks.
I worked it out as follows.
Created a Lookup Work items step in the automation for retrieving open issues that fall onto the Board I'm interested in.
e.g. project = XYZ and status NOT IN (Done) AND component IN (Operations) AND Sprint IS NOT EMPTY ORDER BY Sprint DESC
The sort descending ensures I get the Sprint value on the first listed issue.
Then on the create release step, I use {{lookupIssues.first.sprint.name}}
That's it.
Without seeing your actual rule and audit log details...
Rather than using the list first function, I recommend using list filtering on the sprint's state to confirm it is indeed the active one. The reason is the lookup results are a list, and so is the sprint field, resulting in a list-of-lists. Thus if your work item has been in multiple sprints is will produce a list of names.
Instead, please try this:
AND sprint in openSprints()
{{#lookupIssues.first.sprint}}{{#if(equals("state", "active"))}}{{name}}{{/}}{{/}}
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bill, the first suggestion is good in that by checking the Sprint is open we reduce the # of hits in the list.
As for the 2nd suggestion it's not giving me what I want.
All we need is for the Release (new version) to be the Sprint name followed by the date. And this is working fine for us.
{{lookupIssues.first.sprint.name}} : {{now.jiraDate}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Claudio Rouillon would you please post images of:
Those may help provide more context. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill, see attached, I cannot provide Audit Log details as the rule is yet to run next Monday at midday, but have tested the Lookup Work Items and the Create Version steps with the smart value in another (test) rule and works fine for us.
Claudio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rather than waiting for the schedule, I recommend testing the rule like this:
Then once the rule is saved / enabled, from the ... menu at the top-right of the rule editor, select Run rule and check the log. This will allow you to adjust the rule and quickly test the results.
When everything is working as expected, apply the changes to the earlier rule (or add the actions to this new one).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.