Schedule event to close tickets based on other Jira Cloud tickets

[Csaba Vertessy]

Hello community,

wondering if the following is possible using automation:

Our team works on two (not connected) Jira SM Cloud instances. Some tickets which are assigned to the team on Jira A are created on Jira B using email notification. The Jira issue keys from Jira A is stored in a custom field on Jira B issues.

I'm wondering, is it somehow possible to run on a daily basis an automation which

* from Jira B calls Jira A using the stored issue keys 

* gets the status values of the issues on Jira A 

* transitions the issues on Jira B to the same status (statuses are identical).

Any thoughts on this are welcome!

[Trudy Claspill · Accepted solution]

Hello @Csaba Vertessy 

I think you could do something like that with Automation Rules that use the Send Web Request action to call the Jira REST API.

Start with an Automation Rule on Jira B, with a Scheduled trigger with a JQL to retrieve the issues where the field storing the Jira A issue key is not empty. You may want to add other criteria to keep the list within the service limits of automation, or to exclude issues that are already closed.

Add a Send Web Request action to call the Jira REST API for Jira A to retrieve information about the Jira A issue key. Here is a reference to an article about using Send Web Request and a link to the API endpoint for retrieving an issue.

https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get

You would then have to extract the Jira A issue status from the web response, and use that to transition the Jira B issue.

[Csaba Vertessy]

Hello @Trudy Claspill ,

Sorry for my late answer.

Thanks for the suggestion, I was also thinking about the similar approach.

I'm able to get the status names, but when I try to transition tickets on Jira B I'm ending up with an error 'Unable to transition your issue to the selected status:'

Here are some screenshot:

- No mandatory fields

- Permission checks out

- Replacing in the last step the variable with a selected status will transition the issue.

Any ideas what I might miss here?

[Trudy Claspill]

It does not appear that the transition can be executed based on the variable containing the name of the destination Status. In my own testing I had to use the unique numeric ID associated with the Status as the value of the variable, and then the Transition Issue action was successful.

If there may be a variety of values coming through for the Status, you could use a Lookup Table to correlate the Status names to the unique numeric IDs of each status.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-lookup-table

[Csaba Vertessy]

Thanks, @Trudy Claspill for the suggestions, I was able to get it work.