Schedule event to close tickets based on other Jira Cloud tickets

Csaba Vertessy February 28, 2025

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!

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 28, 2025

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.

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events