My goal is for the Task and Subtask Status to get cloned over as well. My task Status changes correctly, however, the cloned Subtask Status is not cloning over correctly.
I have tried just about every Action/Condition within my For Sub-tasks branch but nothing will clone the Subtask Status properly.
Here's a drawing to further explain my dilemma.
Original Task (Status = To Do)
Original Sub-task (Status = To Do)
-->
Cloned Task (Status = In Progress)
Cloned Sub-task (Status = To Do)
As you can see the Cloned Task status changes perfectly, but the Cloned Sub-task Status does not follow the workflow. The Cloned Sub-task should now have a status of In Progress.
Here is the only error I can find:
See this automation for additinal details on the automation: https://community.atlassian.com/t5/Jira-Software-questions/Clone-subtasks-with-Jira-automation/qaq-p/1321057
Hi brandon.bradshaw@maritz.com
Can you please clarify the logic for your full rule - is it...
Note: I know this isn't strictly how it is in Jira, just trying to clarify how the whole rule works
---
A few questions:
---
Understanding how the full rule works can help to clarify what might be missing here!
Ste
Exactly that, the beginning trigger is actually a calendar schedule M-F. The automation works all the way up until my final branch For Sub-task where it seem to not transition the Status of the cloned Sub-task.
I made some notes below.
---
A few questions:
---
Let me know what else I can eloborate on and if that helps.
Thanks for your time
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi brandon.bradshaw@maritz.com
So just to clarify the rule again:
If this is correct, see below for a rule which does not require the template Tasks/Sub-tasks.
---
---
A few notes on this approach:
---
---
If the "Template Task" is the same each time, the above rule should work.
But if it isn't - and it changes each time (eg. new Tasks get created, and moved into the status "Template" to be automated) - you might need to keep your existing parameters.
So the rule might look something like this:
^ As you have already seen, in this rule's scenario the problem is then transitioning the new Sub-tasks to "To Do" also. I tried a few different options using Advanced Branching, advanced field editing, etc - but I think it might need to be a separate rule
The rule might be...
---
There are several requested features which would help with your need - I'd recommend voting for these / watching them:
---
Let us know what you think!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry Stephan I'm probably making this more confusing than it needs to be. I appreciate all of your help so far.
This board is strictly recurring tasks only. So if you have a task that happens everyday during the week you will add your task to the templates column and give it a label of M-F. My automation simply looks for the M-F label, copies that task and make a new ticket for it in the To-Do column and gives it a time stamp in the title of the ticket. This works perfectly.
We started thinking we may want to add sub-tasks to some of the recurring tasks. For example if one of your recurring tasks was checking an email inbox then maybe it wasn't necessary to have 5 tickets created during the week for that task. Simple to declutter the board. We figured there could be one task with 5 sub tasks. I am now realizing that this won't work completely with the current set up because the M-F label would still create 5 tickets instead of 1 ticket and 5 subtasks. However, I can make a second automtion for a Monday only label.
The core issue is setting the Status of the Sub-task. I believe if you could show me how to hard code or hard set the status field I could use something like this to complete my goal. Is there some sort of code or JQL I can put in this below that will set the Sub-task Status from Template to ToDo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Stephen Wright _Elabor8_ I believe I solved my problem by adding a second seperate rule. It would be nice to understand the JSON that could SET fields. But this works just fine. Thanks for your advice!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi brandon.bradshaw@maritz.com
As I said above, I don't believe this is possible currently - but there are feature requests for it. You also can't set the Status using JSON as it's managed by a different action, "Transition Issue".
You do need the second rule to complete the transition of the Sub-tasks at this point.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How would one know if it's working from this example, because "To-Do" is the default beginning workflow status that cloned sub-tasks receive?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Eric Jahn
You don't need to transition the issue if it remains in the first status post-creation. These additional details/rules are only needed if you're transitioning the issues straight away.
Edit: Answered on your new question.
Ste
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.