How can we move the sub-task along with the parent task.
If Parent Task A if moved back to In Progress from done then how can we move the sub-task of Parent Task A along with it?
Hi @Sohail Alam !
We can do this through an automation rule. We can either create an Automation Rule in the Project or Global settings depending on the scope (and our permissions). Depending on the complexity of your use case, the automation might look like this:
Here is a link to Jira's Automation resources: https://www.atlassian.com/software/jira/guides/automation/resources
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Sohail Alam , that is helpful detail.
Can you help me understand how the new subtask is being created? This does not seem like native Jira functionality so I'm wondering if maybe there is another Automation Rule running that is creating the subtask?
I have an active Automation Rule in our Jira Org that only runs on Tasks where subtasks do not exist. Maybe this can be added where your subtasks are being created?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, I have this rule when Task A is moved from In Progress to Done, it will create sub-task all the time. So if i move Task A from Done to In progress and again from In Progress to Done, it will create 2 same sub-task. And all I want is just one sub-task no matter how many time the ticket status is changed. Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Sohail Alam !
Here is a screenshot of my Related Issues condition that checks that subtasks do not exist before creating one:
This is how I am solving a similar issue. I might add this to your conditions before the action on the automation that creates your subtask so it does not run more than once.
You could also add another layer and add a Label to the auto-created subtask and check that that does not exist if you want to run your subtask automation on issues where other subtasks might exist.
Let me know if you want me to build the second scenario out and provide an example.
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.
That's great news @Sohail Alam !
If it meets your expectations, please don't forget to accept my answer :)
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.
Next to my original answer, right under your question, there is a button to "Accept answer":
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Done, thank you again. I do have another question related to Release notes formatting. Should I create a new question?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you!
This will show that your Question was answered and helps get other questions answered quickly by separating yours from the unanswered ones :)
Yes, I would recommend creating a new question with a new description to get the best response from the rest of the community. I'll keep my eye out for it ;)
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.