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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
I have two projects in our JIRA instance, NPE and OIM. What I want to achieve is that when a release is edited in the NPE project, it will also sync with the OIM project.
Example:
Below I have a release version of 27.55TTPTEST in the NPE project. If I were to edit this to 27.55TTPTEST-2. I want to see this change reflected in the OIM project.
I created a webhook listener in system -> webhook. I then linked this webhook to the automation I created in the OIM project:
This does not seem right since this is looping through issues instead of the "release" in JIRA.
Any help is greatly appreciated it.
Thanks,
Garret
Hello @Garret Zhang
Jira Automation does not include actions for modifying the Release Version name. You can see the supported actions here:
https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/
There are actions to Create Version, Release Version, and Unrelease Version.
There is a Trigger for Release Updated which you might be able to use to detect that the name of a Release was changed. To make a change to a Version name in another project, though I think you would have to use the Send Web Request action to call the REST API endpoint for updating a version.
is it possible to setup webhooks on a project level?
I found a source saying I can find it in project settings -> webhook. But I don't see this option:
Another question is, if I were to setup webhook on the global level, would it work as well?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please provide a link to the document you referenced about webhooks.
I have not worked much with webhooks so I don't readily have an answer on if that solution would work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Garret Zhang, can you elaborate what you'd like to use the webhook for? I don't see the need for it.
If you want to do it with automation, I'd suggest it similar to @Trudy Claspill.
Creation is as easy as:
Updating would be then sth like:
However, this use case would be too tricky for me to recommend. I'd rather recommend an actual syncing app for this use case. But I'm also biased since I work for the team behind Backbone Issue Sync.
You can use one of these version sync apps - our app Backbone also added this feature to sync versions some time last year.
Cheers,
Matthias.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Garret Zhang hi. Diana from ZigiWave here. If you're open to exploring using a 3rd party tools, feel free to check out ZigiOps . It's fully no-code, does not store your data, simply transfers it, and can sync your Jira projects easily.
Regards,
Diana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Garret Zhang ,
Thanks for posing your question here.
In this case I would recommend you to use an integration solution like Exalate.
With Exalate you can create an integration between different projects and also sync Versions (Fix Versions, Affected Versions) with ease.
It also provides you a scripting interface where you can choose to sync only the relevant information with the Target project.
Hope this helps!
Thanks, Dhiren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see:
Atlassian Community online guidelines for Marketplace and Solution Partners
Kind regards,
Bill
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.