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

When we'll be able to archive a ticket with automations rules

Jaquez Jeison

For a few weeks now, we've been able to archive issues, but it's still quite manual... for us, the whole point would be to put issues that have been “Done” for 2, 3 or 4 weeks into archived form, so that they can be consulted afterwards.

Do you have a solution or has it not yet been developed?

Accepted answers

Aron Gombas _Midori_

@Jaquez Jeison It should be possible using this approach:

Use the Send web request automation action...
...to call the Archive issue(s) by issue ID/key Jira Cloud REST API end-point.

Here is an older tutorial that helps with it.

These are already available. Please let us know if you succeeded with it, as it may interest other community members.

All comments

Marc -Devoteam-

Hi @Jaquez Jeison

There is no solution on this.

And based on your requirement, I will say (in my opinion) this is no a best practice.

You can’t archive a subtask by itself, but you can archive its parent issue.

You can't search on the issues when archived, without unarchiving them.

You can't make a report based on the archived issues.

You can only view them from the project option "Archived Issues", unlesee you unarchive an issue.

Archiving should be used (my opinion) on old related information, such as:

Fix Versions not valid
Applications not supported
etc...

Not just because an issue is older then, this might still be relevant based on the achieved functionality or else.

Aron Gombas _Midori_

@Jaquez Jeison It should be possible using this approach:

Use the Send web request automation action...
...to call the Archive issue(s) by issue ID/key Jira Cloud REST API end-point.

Here is an older tutorial that helps with it.

These are already available. Please let us know if you succeeded with it, as it may interest other community members.

Jaquez Jeison

Thank you for your help. Thanks to you, I was able to set up an automation that meets my needs. Much appreciated!

Aron Gombas _Midori_

Awesome!

George Villagaray_5mdnu6

As a BPM, it's a standard and considered best practice in many a business process modeler's career. Archive is a main mechanism for ensuring valid reports and correct data is used.

Heck, closeout (formally closure) is even defined standardly in most PM Waterfall handbooks and BoKs.

Welcome!

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

Quick Links

Find more posts tagged with

issue

jira

cloud

jira-software

jira-cloud