Hi guys,
My workflow system is like the following:
1. When a Story is created, two sub-tasks are automatically created under that Story.
2. When BOTH of those two sub-tasks are marked as DONE, another new sub-task should be automatically created under the same Story.
Here, the most important point is:
Both of two sub-tasks MUST be DONE to get the next new sub-task. If only one of those two sub-tasks is done, new sub-task should not be created.
Thank you so much!
You can do this with Jira's Automation feature in the project if you have project admin. The automation rule would be triggered upon transition of a ticket.
I'm not sure the exact configuration, but basically you'll need to trigger it when sub-tasks close, and have it look in the parent ticket (I think with branches and if statements) to ensure that there are no open sub-tasks. If there are no open sub-tasks, then create sub-task 3. If there are open sub-tasks, do nothing.
That's the jest of how the rule would work. The actual implementation on it, I'd need to spend more time to give you the exact config.
This guide here should also help. https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
Can you provide me more details about your method with something like snapshots of automation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't do snapshots, but maybe this will help better:
Automation rule #1: Creating two sub-tasks when a story ticket is created
Now, whenever a Story is created, two sub-tasks will automatically be created under that Story.
Automation rule #2: Create third sub-task when two sub-tasks are completed
Now, whenever two sub-tasks are marked as "Done" under a Story, a third sub-task will automatically be created under the same Story.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for all the details? Heather!
Since I know how to the Automation rule #1, let’s focus on rule #2.
For step 6 and 7 above, you mentioned “Compare Condition”. But according to my JIRA automation components, there is no “Compare Condition”. There is “Advanced Compare Condition” instead, but when I click on it, the first value does not have any “Dropdown”, only JQL version typing system.
I am not sure if we are using the same system, but anyways, is there a way to make it work using “Advanced Compare Condition”? Or is there a way to find “Compare Condition” that you mentioned?
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.
Hi Heather,
Now I have another question. So, according to your automation steps, where is step for fields of those two subtasks?
when those two subtasks get created after a Story is created, those two have different specific Labels, and those need to be called into the automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Caleb Park
You can always add in a step 16 or more for editing the newly created issue and making the edits needed to have the specific labels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Heather,
I actually meant specific Labels for those TWO subtasks that need to be done together, not newly created issue.
For example, your step 5 mentions about “Issue Transitioned”, so I understand I can make it like: “When” something is done.
But step 7 just says that “Number of linked issues” is equal to “2”. Where do I put information about those “two” subtasks? For instance, those two subtasks have specific Labels. And I think the specific Labels should be called for “Number of linked issues” stuff.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the screenshot I shared, you can always call out additional requirements by adding more conditions. So you can add in the fact that labels have to equal certain terms.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Heather,
Thank you for your help, but another question is:
In related Issues Condition, Condition only has 4 options like the following:
There is no "Are Greater Than" under Condition dropdown option. Is there any way to make that option?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.