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
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
I am having some trouble figuring out the best way to use JIRA to handle the release of a new product. The manual process currently being used is:
1. Declare a new release should be done
2. Person A prepares a release (bumps version, packages software)
3. Person B does some final testing on the packaged release
4. Person C does the distribution
One thought I had was to create a new issue type called “Release” and then create workflow that would take the process through the stages mentioned above.
However, since this process should a common one (but maybe it isn’t) and there doesn’t seem to be direction and default support for it in JIRA, I figure I am over thinking things and there is a way that JIRA should be used to manage this.
Any and all comments are welcome.