Create rule on 'Archived Issues NEW' feature?

[Joe]

I would like to create a rule when I archive an issue.  I am referring to the new feature that was called out here from the cloud chnages in 12/9 - 12/16

My data is sync'ing to Align and there isn't any support on the Align side for items being archived.  

Any thoughts if this 'archiving' is supported anywhere in automation rules?  I'd just like to add a label of ARCHIVED when an issue is archived.

Thanks

[Bill Sheboy]

Hi @Joe 

I do not believe there is a publicly-available event for archiving an issue with Jira Cloud (unlike Jira Data Center which has one) and so a rule could not be triggered when archiving happens.

After a quick check, I did not find an open suggestion to add this feature in the backlog, so you could do so by giving feedback to Atlassian.

Kind regards,
Bill

[Joe]

Thank you Bill, did just that.

[Julian Governale]

Hi @Joe ,

I have successfully implemented an automation rule that will archive issues based on my JQL

Here are the steps I used, jql updated for this example

API: The Jira Cloud platform REST API

1. Trigger - Scheduled  - runs on the scheduled specified
2. Action - Send Webrequest
   1. URL: <site>/rest/api/2/issue/archive
   2. Method: POST
   3. Headers
      1. accept:  application/json
      2. content-type: application/json
      3. authorization: API Key
   4. Body - Indicate your JQL in the body
      1. {
         "jql": "project = XYZ and labels = archive"
         }
   5. Check off "Delay execution of subsequent rule actions until we've received a response for this web request"
3. Action: audit log
   1. {{webResponse.body}}

Capturing this webResponde.body in the audit log will provide you with a task URL and ID to check the progress of the web request

For your request, you could do the same, but before running the web request, you do a lookup issue and then an edit issue action add the label, re-fetch the data, and then archive the issue, i.e. update your JQL to be based on the label of "archive".  Alternatively, you set your trigger to be based on the field change of labels and then evaluate from there and call the web request. 

Let me know if this helps or if this way off on what you were looking for

[Bill Sheboy]

Hi @Julian Governale 

I believe this question is about detecting that an issue has been archived and not performing the archive itself.  (The second one has been answered in the community many times before.)

Kind regards,
Bill