Any API/script to retrieve the issuekey/issueId of the Xray issue that is updated using importer.

Nithu Brijita December 13, 2024

 

 

My application relies on webhook events in Jira Data Center (DC) to trigger actions and send payloads to Cosmos. However, there is no webhook event being triggered when test/testcase/tesplan is imported into an Xray issue using testcase importer. This discrepancy is causing a mismatch between the issues in Cosmos and Jira. I am seeking assistance to identify if there are any APIs or scripts available that can help me retrieve the issue keys or issue IDs where these imports occur. Any guidance on addressing this issue and ensuring synchronization between Jira and Cosmos would be highly valuable

2 answers

0 votes
Manuel
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 18, 2024

Hi @Nithu Brijita , @Stefan Stadler  is correct; as these are issues, you can implement logic like listeners that react whenever your Xray specific issues are created

Regards

0 votes
Stefan Stadler
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 16, 2024

Hi @Nithu Brijita 

I have used XRay before as well and if I remember correct, all the stuff is also considered to be stored as issues. At least for tests, there should be some kind of issue type available.

If that is the case, you could react to the creation of such issues and then do some checks. Unfortunately, I do not have XRay available, so I cannot verify my assumption. However, that would be my way to try first.

However, I also remember that the connections between the different issues are not always that easy to use with help of Jira Automations. I have been using ScriptRunner listeners for this.

Let me know, if my assumption is correct and if it helped :)

Stefan

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events