You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
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
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.
TBH I use webhooks to communicate between different JIRA projects without a middleware.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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}}"
]
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.