Hi all,
New to Jira automation here!
We use our Jira with what I assume is a fairly standard model between service projects and software projects, using linked issues with blocks/is blocked by. Standard process is:
The problem I'm having is building a set of rules in automation which provide the specific responses needed, which are
Looking at available options in automation, I'm not sure if the needs I'm looking to fulfil are too granular and quite simply can't be built for these purposes.
Does anyone else run a similar model and have automation set up in this way? Any general advice would also be appreciated on whether this isn't going to be achievable.
Thanks
Hi @Chris - Welcome to the Atlassian Community!
Adding to the ideas Curt suggests:
Are you using one or multiple projects to manage the "service project", "feature request", and "system issue" Jira items?
If these are multiple projects, some of your rules would need to be global/multi-project scoped...and, depending upon your Jira license level, you could encounter some limitations on rule executions.
Kind regards,
Bill
@Chris Your current branch will include both the linked and Sprint squad issues, as you have both Blocks and Is blocked by links in scope.
The problem is it depends on how people do the linking. If they are always doing it the one way, work out which way that is and set it up accordingly (i.e. just "is blocked by").
To test it now. create a scheduled trigger with JQL "sprint IN openspirits()" then do a branch with just one of the link types and have the comment action. Run it right away and see which ones get the comment (use the audit log of the rule).
Change it to the other link option and see how that plays out.
To get this tight, you may well find there needs to be a education piece on the correct way to do the linking to guarantee the rule can be relied upon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Curt,
Thanks for speedy reply, I've set each of these up, the below is for new issues added to sprint
I'm unable to test until next week when new sprints begin. For leaving comments on the linked issue rather than the sprint squad ticket, does the above look correct to you? And are my if/and statements going to be doing JQL checks on the linked ticket rather than the squad ticket? Apologies for the noobiness...
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Chris
Welcome to the community.
All of this should be possible.
For 1 & 2 do a rule like this:
Trigger: Sprint started
Condition: If/Else statement
If
JQL condition (with JQL to find all the issues in scope and sprint = Active sprint)
Then send an email or whatever "A new sprint has begun and your ticket has been included"
Else
JQL condition (with JQL to find all the issues in scope and sprint != Active sprint)
Then send an email or whatever "Your ticket hasn't made it into a sprint yet"
For 3
Trigger: Sprint Completed
Condition: JQL (with JQL to find all the issues in scope and sprint = Active sprint AND statusCategory != Done)
Action: email or whatever "Your ticket wasn't completed in 1 sprint cycle and has been added to the next sprint"
For 4
Trigger: Issue transitioned (to whichever "Done" status category Statuses make sense)
Condition: JQL (to find all the issues in scope)
Action: email or whatever "Work for your ticket has now been completed and is deployed live"
Alt version:
Trigger on Version released (if using versions?)
Hopefully this helps?
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.