nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I need help building an automation that will recur a work item that has been resolved for 6M.

rworkman

I have a work type called Blog that after it has been Done (or on our board Published) for 6 months, I'd like --

1. The summary to update to: [6M Review] {{issue.summary}}

2. The status to update to: Coming Up

3. The due date to update: 30d after this trigger

4. Re-assign to: xxx

I am trying to use Rovo to build this automation but I can't tell if it's working because I don't technically have any blogs posts that have been done for 6 months. When I try to update it 1M to test, I don't get any results.. so I'm assuming it's not working.

To test it, instead of updating the task, I want the automation to even just send me the results of the query in my email, so that I could just review what tasks need to be updated and just manually do it (FOR NOW, would prefer the automation but I don't trust it yet to update my tasks).

Help!

Edit -- Here's what I asked Rovo: For blog tasks, 6M after being transitioned to Done, I want the following changes to automate: I want the summary to change to "[6M review] {{issue.summary}}" and I want the due date to update to 30days after the trigger and I want the assignee to update to Robin and I want the status to update to Coming Up.

What Rovo built:

Screenshot 2026-03-17 at 9.44.41 AM.png It looks good? But what I'm nervous about is the JQL:

project in (12222) AND (status = Done AND updated <= startOfDay(-180d) AND issuetype = Blog)

"<= startOfDay(-180d)" is what makes me nervous. How do I know if this only triggers issues on that exact day. I don't want it to continue triggering issues that are 6M+1day, etc.

Accepted answers

All comments

Christopher Yen

Hi @rworkman

Did rovo create an automation rule? If so can you post a screenshot of it?

The route I would take (may not be the best route) would be when a Blog transitions to "Published" that you update a custom date field to current date + 6 months and then create a scheduled automation rule that runs daily searching for Blogs with that custom date field = current day and if so transition it to "Coming Up" and then edit the work item for the due date and summary edits you mentioned. Just keep in mind if you do [6M Review] {{issue.summary}} by the next run it will be [6M Review] [6M Review] {{issue.summary}} and so on.

with that setup you can do some test cases by manually setting that custom date field and running the automation rule.

Yelizaveta Otroshchenko

@rworkman

Hi. Maybe this option could help you.

I don't have any tasks that were created 6 months ago, so I added a custom field with type "Date Time Picker" to simulate this. In my case field called "Date of created".

So we have ticket PRG-1 and a summary "Help task 1". This ticket was created Sep 03, 2025, 2:00 AM.

1. In a trigger rule, choose "When: Scheduled Every day at 12:30 AM". That means that the rule will be triggered every day at 12:30 a.m. You could choose another time.

2. Choose "FOR EACH: Add a branch" –> "Branch rule / related work items" –> "Type of related work items = JQL" (project = "<Name>" AND issuetype = Blog AND Created <= 6M)

3. For this step, I add a new custom field "Old summary". Copy current summary in this field. In the future, we will use this date to created new issue's name.

4. Re-fetch date in task. This action updates and saves ticket changes.

5. On the next step, we choose Transition.

Transition – Coming Up

6. Change issue Summary - [6M Review]{{issue.summary}}

Set up Due date - {{now.plusDays(30)}}

7. Choose Assignee

8. To verify, we run the rule manually.

9. Check result

rworkman

Good point.. how do I solve for the [6 month] duplicate? Can i get the automation to check the summary? It would be awesome if it could track if [6M] already existed and then add [12], [18], [24],... etc.

I added Rovo details into my original post. I like your idea of a custom field time for review. I still wonder if I can brain a way to track how many iterations of the [6M] review have taken place..

rworkman

I think im following here and this could work. I'm confused the purpose of step #3? Is that so we don't duplicate [6M Review] in future iterations and only pull the original summary?

In JQL, will "Created <= 6M" pull issues with created 6M+1day, +2days,...etc?

rworkman

Also! Would you have any suggestions on how to retroactively add this custom date field for the blog tasks that have been completed <6months ?

Christopher Yen

Hi @rworkman maybe you can try to invoke a rovo agent in an automation rule and prompt it to add 6 to the number within the brackets each time it runs and use the agent response smart value to replace the summary. I would test with a manual trigger first.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk-cloud

jira-service-management-cloud

jira-service-management