We are trying to automate our workflow. Here is what we would like to do:
We want to change the status of a parent issue (a story) when the status of one of its children changes. For example, suppose I have a story on the backlog that has 5 children that are also on the backlog. As soon as one of those children transitions from the backlog to an "in progress" state, I'd like to update the status of the story to have the status of "in progress" as well. The story would then stay in a status of "in progress" until its last child not yet in the state of "done" moves into a state of "done". At that time the story would be moved to a status of "done". We'd like to do this in an automated way so we never have to actually change the statuses of our stories.
Is this possible with your plugin? If we we'd love to know how to accomplish this. I can see how I would auto transition all subtasks from a change on the story, but not the other way around like we need it. There are lots of people trying to do the same thing online and there is really not a simple way to do it other than scripting it yourself. I am hoping Automation for JIRA can make this a bit easier.
You can certainly do this with Automation for JIRA. The rule is a little complex, but here's an example:
So lets break this down:
The 2 'related issues' condition inside the two branch points, basically make sure the two branches are mutually exclusive and only one will ever execute. Hope this makes sense!
Yeah so you could definitely restrict this further using the JQL condition and/or related issues condition to only run this rule when certain types of sub-tasks are transitioned.
The 'Parent' condition is actually an our 'Branch / Related issues' action. It's a way to fork rule execution for related issues of the trigger issue.
There's an number of different options available to find related issues:
(these are all in relation to the trigger issue)
So in other words, you can find the 'Linked issues' of a trigger issue, or you could find the Epic of the trigger issue etc.
Hope that helps!
@andreas any news on my question above?
Epics I want to transition are on "Operation" projects only.
Linked issues can be of any type (bug, task, story, incidents and subtasks) and from different projects "Web Crawling" and "Application" with same workflows statuses.
I have Global rule config and all are on create screen already.
I tried with this other rule not on an Epic but on any Task, Story, Incident or Bug to transition from one status to another depending on his linked issues statuses, but is not working.
I branch out for elseif conditions the "For Current Issue" to apply on different status for his linked issues.
I work on a cloud version and this works fine for me:
We have a parent project called "Operation" and have several software factory related projects (Web, Data, Crawling, App) that transition the parent status issue based on their status issue.
(1) Rule must be global
If issue matches JQL transitioned is in any other project than the parent project "Operation" and is not an Epic (we use them on App, Web Crawling, Data, and others) then:
For Linked Issue (Types: can be "blocked", "is blocked by", "causes" relationships):
If: Issue matches JQL condition takes out the parent project and the "status" of the parent issue is going to be transitioned:
Based on some of the statuses of the related issues:
(for example, we change the parent status to "In Progress" if some related software factory issues transition to "QA", "Code Review", "In Progress", etc)
I am trying to so something a little different. I have a project that when it needs to be escalated it creates a new ticket in another project and automatically links the two. the issue i am hitting is, that i want the linked ticket (the child) when moved, to update the status of the original ticket ( parent).
I may be missing something, but i cannot get it to work. @andreas any help would be great!!!!
I have a rule working to do this fine in Cloud, albeit a simpler approach as I only want to watch a single transition.
My teams tends to grab their subtask and get to work, forgetting to update that parent "Story" level status, which is all that really matters to the PMs (and myself) in most cases.
In simple English...
WHEN a subtask is transitioned from 'STATUS A' to 'STATUS B'
AND the PARENT is in 'STATUS A'
THEN TRANSITION PARENT to 'STATUS B'
The problem I am having is that the assignee of my parent story is being set to AUTOMATION FOR JIRA when this rule runs which was not part of my automation rule at all.
Is this an automatic function or something?
Any input is appreciated. This is only my second rule using automation for Jira Cloud.
Thank you!! 😃
I hope you already have found the answer, but otherwise I have 2 options for you (in Jira Cloud):
I really wanted to help you in this (if still applicable/necessary) because your screenshot helped me to set up my own rule. So thank you again for that! 🎉 👍
And although I am writing this at 5 AM in the morning (couldn't sleep), I am still genuinely grateful that you shared your ideas! Seems like a nice #hashtag to me '#genuinelygrateful' 😃
Kind regards and have a great day today!
I just used this help page to change the status of a story when one or all of the sub-tasks status changes. This might help with any parent/child relationship, such as Epics and stories/tasks.
Not sure about the board part...you might check this page out for popular automation templates:
Hi all, After many months of work, I am delighted to announce the launch of the Jira Automation Template Library! The Template Library is a new website dedicated to all things Jira au...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events