Create JIRA issue using webhooks

siddhesh January 2, 2020

Hi,

 We are using JIRA service desk and JIRA Software.

 Now, I want to add automation rule in JIRA Service desk issue,

when new issue create in JIRA service desk project then it will create clone of the issue in JIRA software project and link to JIRA Service Desk project issue

Is there any automation rule or webhooks are available?

I can perform this using add-ons, but without using any add-ons is it feasible? if yes, how?

Thanks in advance

Regards,

Siddheshwar

1 answer

0 votes
brbojorque
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 3, 2020

Hi @siddhesh ,

This is possible, you are right a webhook is needed and no add-on needed.

I would solve it by having a middleware it may be a AWS Lambda, Ngrok or Heruko.

The flow will be.

JIRA --> Middleware --> JIRA

  • An issue will be created and the webhook will be triggered
  • Middleware will accept the webhook request
  • Middleware then create the ticket and link using the REST API.

While its true that you don't need an add-on but we will need a third party service to accept the webhook request and then process it by yourself which means you need to know how to code.

Marcel Gromball February 3, 2022

TBH I use webhooks to communicate between different JIRA projects without a middleware.

Like Majo Francis likes this
Majo Francis August 21, 2022

@Marcel Gromball May I know how did you manage to achieve that ?? 

Marcel Gromball September 1, 2022

@Majo Francis Sure, i used Automation in one project to accept webhooks for issues on the board. I used the automatic generated url. I then use stuff like:


if {{webhookData.status}} = Closed then Update the Issue from the webhook on this board....


 

On the other Board i use send Webrequest and place the url from above but add :


?issue={{issue.customfield_10014}}


to the end of the url so the other project can access the right issue. The customfield_10014 is the Epic Link for me as i linked both issues.

 

Inside the webrequest i have the following settings:


Content-Type application/json

POST

custom data:

{
    "status": [
        "{{issue.status.name}}"
    ]
}


Like Majo Francis likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events