Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Better way to retrieve Jira Issue Keys from Gitlab

Davyd Derkach August 14, 2024

Hello everyone!

I have a Jira integration with Gitlab, as well as some automation on screenshot below that receive a Jira Issue Keys related to current release tag from webhook, parse them, send a message to Slack and preform simple transition:

  image_2024-08-14_103835128.png

Here the webhook that i use to send Jira Issue keys that related to current release from my pipeline:

 

curl -X POST -H 'Content-type: application/json' --data '{"data": {"keys": "BDO-392,BDO-391"}}'https://automation.atlassian.com/pro/hooks/<your-webhook>

Question:  So I am wondering is there a way to receive Jira Issue keys as well as some metadata such as Release Engineer name, release date and Jira Issue Summary in some other way rather that running script and sent this information via Webhook URL? 
I found that there some "smart values" that should be available after integration with Gitlab:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/

But I am wondering whether these values are available and how to use them to sent message to slack with following information:

 

Jira Issue keys related to current release tag as well as some metadata such as Release Engineer name, release date and Jira Issues Summary.

1 answer

0 votes
Adolfo Casari
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.
August 14, 2024
Davyd Derkach August 15, 2024

@Adolfo Casari

Thanks for your reply. I am already using {{webhookData}} smart value to parse my webhook body.

But my question is other: Is in my case it`s a correct way to use a script that sends the Jira Issue keys that related to current release to my automation rule via webhook like this:

curl -X POST -H 'Content-type: application/json' --data '{"data": {"keys": "BDO-392,BDO-391"}}'https://automation.atlassian.com/pro/hooks/<your-webhook>

Maybe it`s possible to not use script and get all needed values:
Release Engineer name, release date and Jira Issues keys that related to current release?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events