I am Scrum Master of Infra Team. We typically deliver DEV, TEST, PrePROD, PROD capability for various application teams.
I want to use Release functionality in JIRA to plan my infra releases down the line.
I am thinking of creating DEV Release, TEST Release, PP Release, Prod Release placeholders for my planning.
Whatever Epics/Stories I will deliver for DEV Release will also need to go in for TEST Release and few additional more (may be), and to PP Release and so on so forth.
So the question is, will I be able to fall-over/take-forward my already "released Epics/Stories" onto my next release DEV->TEST->PP->Prod etc and "release them again"?
OR in JIRA, once a Epic/Story is released, it is sort of Done-Done and can't be taken over again "to be released" for next release?
Typically a release would be used only "once". Meaning stuff that is released is considered Live/Production.
I would not personally suggest to use releases how you describe them.
You could surely introduce a new metric for keeping track of the stages where your code is though. Either simply a status in the workflow, or either a custom field/label/linked issue, etc.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events