How to create a repeating issue?

[Dominik Saban]

Hello guys,

I would like to make a couple of issues repeat themselves on certain days. For example, I would like certain issue to repeatedly return from 'done' to 'selected for development' without changing the Cumulative Flow Diagram. I tried making an automation, got stuck on JQL search. I finished atlassian course on Jira, but automations were not covered. I cannot find anywhere detailed instructions on creating automations. Can anybody explain it to me step by step? Below is a screenshot of what I tried to do.

Thank you so much, anyone willing to help!

[Bill Sheboy]

Hi @Dominik Saban -- Welcome to the Atlassian Community!

First thing...what problem are you trying to solve by doing that?

A cumulative flow diagram (even Atlassian's interpretation of one) shows the count of items in a particular process step over time.  This helps to learn about a team's process flow, identify measures to help, and identify symptoms of problems requiring action.  Changing an item from "done" back to "not done" does not make sense to not impact the CFD: this is changing an existing item.

Instead do you want to create a new item, which is a duplicate of the prior one?  For example, for a re-occurring report?  If so, consider cloning the existing item when it reaches your done step.

Next, automation rules in Jira require both learning and experimentation: there are no shortcuts.  To get you started on creating your rule, please refer to these documentation and example sources, and information on creating JQL queries...including a free class from Atlassian University: 

• https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
• https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/
• https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql

Finally, if you run into challenges creating your rule, please post images of your complete rule and the audit log details showing the rule execution, and explain what is not working as you expect.  This will provide context for the community to offer suggestions.

Kind regards,
Bill

[Diogo Teles]

Hi @Dominik Saban 

Welcome!

Before automatically re-opening an issue, it's important to consider the impact on metrics and data accuracy. Re-opening issues can negatively affect metrics unless corrective measures are taken, and built-in reports may not accurately reflect the changes. With that in mind, here are some tips for automating the re-opening of issues:

1. Identify the issues you want to re-open: If you want to re-open all issues of a specific type, it simplifies the process. Alternatively, you can tag an issue by adding a label when it transitions to the "Done" status (you can use automation for this step as well).

2. Determine the reference date: If your workflow marks an issue as resolved when it transitions to the "Done" status, you can use the resolution date as the reference point.

3. Set up a rule with a scheduled trigger: Configure the rule to run on a regular basis, such as daily. Use JQL on the scheduled trigger to limit its scope to the issues with that label.

4. Use an advanced compare condition: Compare the number of days that have passed since the resolution date to the desired threshold for re-opening. For example, if you want to re-open issues after 10 days, use the following condition:

Advanced Compare condition:
if
{{now.diff(issue.resolutiondate).days}}

=
10

5. Set an action to transition the issue: Configure the action to transition the issue back to a previous status. Make sure the issue workflow includes the necessary transition and a post function to clear the resolution field.

6. Optional: Remove the label: If you used a label to tag the issues for this rule, add another action to remove that label, ensuring it's no longer associated with the re-opened issue.

By following these steps, you can automate the re-opening of issues based on specific criteria while being mindful of the potential impact on metrics and data accuracy.

[Diogo Teles]

Forgot to add, you can check this documentation on working with dates in automation

Jira Smart Values - Date and Time 

[Olha Yevdokymova_SaaSJet]

Hello, @Dominik Saban   !

If you are okay with add-ons I would like to suggest using the Recurring Checklist and Reports add-on developed by my team, which may help with your needs. With this add-on, you can create recurring task with any information or checklist inside automatically based on preset rules. The interface is very straightforward and you can set dates, times and recurrence for you tasks.

You also can choose multiple assignees for the tasks if you will have more than 1 person with the same task and anyone will receive new task with the notification about its creation.

With the ability to reporting in this add-on, you can also check report for the submission dates of all your employees and information from the checklist in one place.

I hope this helps and let me know if you need further assistance!