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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,026
Community Members
 
Community Events
184
Community Groups

Check if a Version/Release already exists

I want to automate release creation. For that I would love to check if a release already exists, so that there are no duplicates. How can I achieve this in Jira Automation?

1 answer

1 accepted

1 vote
Answer accepted
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2023

If there isn't a more convenient approach, you can always use the "Send request" action and work with the Jira Cloud REST API.

In this case, you can query the versions in the project. And then look up the version's name in the JSON. (You can even test if the string "1.2.3-beta" occurs in the JSON string for a low-cost solution.)

Thank you Aron. That looks nice.

What is the best practice for authorization? I'd not like to put my credentials in and the automation user does not allow reading the versions as it seems.

Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2023

Although this article was written 3 years ago, I think the best (and only?) option is still generating an API token, then encoding this to an auth token. 

The problem is, that I cannot add a limited local user in Jira Cloud and I do not want to add my admin credential API keys in the automation.

Is there any way to get to a limited scope API credentials or have the automation user do this somewhat "locally"?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events