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; } } }

Automation: Move issues to a story if they haven't been touched in over a year.

Joe_26234f

We have a story called "Recycle Bin"

I would like to convert tasks/bugs/Stories etc. to subtasks of that story if we haven't updated the issue in over a year.

I can do it by hand, but I wanted to automate it once a week or so.

Not sure how to set it up as I'm new to automation.

Thanks.

Accepted answers

Kalyan Sattaluri_iinm1n

Hello @Joe

Welcome to the community. Jira automation does not give a native way to change issue type.

Based on @Trudy P Claspill notes, I checked and I guess we cannot change it to sub-task even through API.

May I suggest, instead of making them sub-tasks, leave the issue type as it is, but create a "recycle bin" epic and link all such issues to that epic if its been more than 1 year?

This can be easily accomplished through automation but not sure of value add.

But in the end, you have to decide if you want to keep them around after such long time of inactivity.

But automation does have a "send web request" action, using which you can use to change the issue type. It is an advanced topic and community can help if you are interested.

Your rule will look like:

Trigger - Scheduled with JQL -> updated < -365d

Action - Send web request to your Jira instance to update issue type.

All comments

Kalyan Sattaluri_iinm1n

Hello @Joe

Welcome to the community. Jira automation does not give a native way to change issue type.

Based on @Trudy P Claspill notes, I checked and I guess we cannot change it to sub-task even through API.

May I suggest, instead of making them sub-tasks, leave the issue type as it is, but create a "recycle bin" epic and link all such issues to that epic if its been more than 1 year?

This can be easily accomplished through automation but not sure of value add.

But in the end, you have to decide if you want to keep them around after such long time of inactivity.

But automation does have a "send web request" action, using which you can use to change the issue type. It is an advanced topic and community can help if you are interested.

Your rule will look like:

Trigger - Scheduled with JQL -> updated < -365d

Action - Send web request to your Jira instance to update issue type.

Trudy P Claspill

Hello @Joe

Welcome to the Atlassian community!

"Move issue" and "Convert to subtask" are not functions that are supported in the native Automation Rules feature. Each of these actions can require input from the user to correctly map data (setting additional required fields in the destination issue type, mapping an unavailable Status to a Status that is available in the destination issue type). The potential complexity of these actions has meant they have not yet been supported in Automation.

You can find several posts on this topic by doing an internet search for jira cloud automation convert to subtask. If you do that search you may find somebody who proposes a work around.

You could produce a rule that would notify you via email of issues that qualify for the conversion. Given there are limits on the number of rule executions allowed per month you may want to instead set up a Saved Filter and Subscribe to it to get periodic notifications. With that notification you could convert them manually.

Joe_26234f

I will talk to the team, and perhaps implement this. We might also move the status to done, but that is doable.

Thank you for the suggestion, I appreciate it!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud