JIRA web hook to accept JIRA current issueID

[Devendar Gangapuram]

Hi Team,

We are triggering Jekins job from JIRA using a WebHook, (http://XXXXXXXX/jira-trigger-webhook-receiver/), it is working absolutely fine.

Now our requirement is to pass current selected JIRA ticket key(IssueID) to Jenkins job to capture and in return send "Build status" .

I had tried http://XXXXXXXX/jira-trigger-webhook-receiver/{issue.key} but didn't work,

Please provide us the JIRA web hook which can carry jira issue ID as attributes .

Thank  you,

Dev G

[Mahesh Shinde · Accepted solution]

Hi @Devendar Gangapuram ,

As per my understanding, your team must include Jira issue keys (e.g. JIRA-123) in their commit messages (for deployment information) and in branch names (for build information). Whenever a pipeline runs in Jenkins, it will look for Jira issue keys in the branch name and commit messages. If it finds issue keys, it will send build and deployment information to Jira. If it doesn’t find issue keys, the Jenkins plugin won’t send anything to Jira.

Regards,

Mahesh Shinde

[Devendar Gangapuram]

@Mahesh Shinde ,

Thank you so much for the quick reply.

We are not doing any code developement or any commits here. Just using JIRA to pass " BuildNUmber" and "Environment Type" to trigger Jenkins job and do build/Deploy. using JIRA web Hooks.

So my query is: 
When a build is triggered in Jenkins due to status change of a JIRA agile project task, Jira issue details are not passed on to Jenkins.
How to configure "Issue attribute path" to fetch the "JIRA issue ID" of the issue and save it in a Jenkins parameters.

Thank you,

Dev G

[Devendar Gangapuram]

Issue attribut path made this wokred. No need to pass any buitldwithparams in webhook.

Simple web hook URL  http://XXXXXXXX/jira-trigger-webhook-receiver/ worked and with "Issue attribut path " in jenkins side make it worked.

Thank you,

Dev G