Hi!
I do not have a big experience with Jira Automation, but I would like to go deeper into it.
So, my task problems are now:
My idea is to clone an existing record and change the status of the old one. It should be done one year after and also send an email.
For the date I will use:
When: Scheduled and JQL: Project = "SUP" and "Assessment Date" = startOfDay(-1y)
1) I hope it will work like this, but how to clone an issue with different status?
2) Can I create an issue but with the same name and different status?
Does anyone have experience with that?
Example, what I have tried, but it's not correct:
Best regards,
Vladimir
Hello @Vladimir Sumilin
I understand that "score" is an issue type. Is that correct?
And when for a "score" issue, when today is 1 year after the Assessment Date in that issue, you want to create a new "score" issue that is a copy of the original issue. Is that correct?
And you want to send an email to somebody with the key of the newly created issue. Is that correct?
I am confused about what you want to do with the Status. I think I understand that you want to change the Status of the original "score" issue. Is that correct? What do you want to change it from and to? Also, does the Status of the original "score" issue affect whether or not you want to make a copy of that issue?
What type of field is Assessment Date? Is it a Date field or a Date/Time field?
You could use a Schedule trigger to select the issues based on a JQL:
project=X and type=score and "Assessment Date" = (-1y)
The remainder of the rule actions will execute for each issue retrieved in the Schedule trigger JQL.
You could then use the Clone action to make a copy of each issue retrieved. The new issue will automatically be created with the initial Status for the workflow that applies to the "score" issue type.
If you want to change the status of the original issue, then you would use a Transition action to change its status.
And then you can use the Send Email action to send an email about the new issue you created. To insert the key for that newly created issue into your email use the smart value {{createdIssue.key}}.
Note that using the Clone action will not cause the children issues of an Epic to also be cloned, nor the Subtasks of an issue to also be cloned. The Clone action will copy only the main issue.
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.