Create Scheduled Automation Monthly for 20 individual repetitive task

[Jason Spellman]

I would like to know if I can create a monthly automation process within Jira that creates a series of new tasks that will follow the steps:

1-Refresh (Person A), once completed it will go to Person "B"

2-QA (Person B), once completed it will go to Person "C"

3-Push to Prod (Person C), once completed the user will close the issue. 

I believe I will have to create 20 individual automated process for each task.

What is the best process, to create monthly scheduled automation for each task. 

Thanks in advance for your time and assistance.

[Richard Scholtes]

I think it is possible to be triggered monthly, but the tasks you mentioned seem to still be needing manual interference by users. With more details I might be giving you more detailed solution according to your real use case.

[Harsh]

Hi @Jason Spellman 

I think you can achieve this. But would like to know, what exactly is QA in Point 2. And what do you mean by Push to Prod (point 3). 

Also are the new task same every month ? 

Another question - go to Refresh A or go to Person B means assignee?

---

[Jason Spellman]

Was able to accomplish this by the following:

When Scheduled: First day of the month at 9:00 AM

Then: Create a new

Task

in (Specific Project)

then create branch

For: Most recently created issue

Then: Transition to Backlog

And: Assign the issue to "Person A"

And: Send Email

Then when Status Equals In Progress

Assign the issue to "Person B"

And: Send Email

When Status Equals: In Review

Then: Assign the issue to "Person C"

And: Send email

[Harsh]

Hi @Jason Spellman 

Yes this can be achieved, but the catch is you have to create multiple automation, since JIRA automation does not allow multiple trigger in one automation rule.

So in your case - there will 2 or 3 automation:

Automation 1: Creation of task.

1. In this rule setting, select the project you want to set the automation rule for

2. Select Trigger - Scheduled. Use Chron Expression : 0 0 1 * *. Here check in option: When the rule executes: simply run the conditions and actions without providing issues.

3. Select Action - Create Issue.
Select the project (I believe the same project).

Select issue type (TASK) and other fields with you want to fill in. Note that Summary is mandatory so you have to do that. And also, you can create multiple issues as well if you need to. Note: The same automation will be created every month with the same name.

4: Choose Branch. Select the type of related issues (in this most recently issue.)
Under this if you want to verify based on some condition you can do that. Or direct choose action - 
           1.  Transition to Backlog

           2. Assign the issue to "Person A"

           3. Send Email

Now create AUTOMATION 2: lets call: In Progress

1. In the rule detail choose the project same as in automation 1 from above. Make sure to check in - Allow Rule Trigger (Since it is dependent on Automation 1)

2. Trigger: When Transitioned from BACKLOG to IN PROGRESS. My recommendation to add a condition as well to check where Assignee is PERSON A. Because there will be other issues as well which will transitioned to INPROGRESS (which is not created by the automation 1). It is your wish.

3.  Choose Action - 

    1. Assign the issue to "Person B"

    2. And: Send Email

And then finally create AUTOMATION 3: lets call: In Review

1. In the rule detail choose the project same as in automation 1 & 2 from above. Make sure to check in - Allow Rule Trigger (Since it is dependent on Automation 1 & 2)

2. Trigger: When Transitioned from IN PROGRESS to IN REVIEW. My recommendation to add a condition as well to check where Assignee is PERSON B. Because there will be other issues as well which will transitioned to IN REVIEW (which is not created by the automation 1  & 2). It is your wish.

3.  Choose Action - 

    1. Assign the issue to "Person C"

    2. And: Send Email.


Hope this helps. Please update if this works. 
Thank you. :)