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.
Hi All,
Please suggest me, how to achieve the below requirement.
1) In JIRA issue create/update page:
Field name - text | Field name- text | Field value - dropdown |
Component 1 | Release version | No relese,r1,r2,r3.. |
Component 2 | Release version | No relese,r1,r2,r3.. |
Component n | Release version | No relese,r1,r2,r3.. |
Note: Field name – ‘Components n’ – These fields are static to the ESPN application.
The field name ‘Release version’ should be populated based on the available release version for the selected component, environment and BU region in JIRA.
2)In JIRA workflow:
In the SW Release (IT Operations) or in Deployment JIRA workflow, when the issue is in ‘To Deployment’ status if the RM clicked that button then the ‘In progress’ transition should trigger the post function which will trigger the customized bamboo deployment plan. If the Bamboo deployment result is a success, then the issue should be transitioned to next state ‘Deployment Completed’. If the bamboo deployment is a failure, then the issue should be transitioned back to ‘To Deployment’.
The custom Bamboo deployment plan URL is framed using the custom issue field recorded in JIRA variables
Hi!
What about the webhook ?
Also, you can automate it
https://github.com/atlassian-api/atlassian-python-api
Cheers,
Gonchik Tsymzhitov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.