Does anyone know the best way to structure release content. I have an Epic with several stories that all have to be released together. This is a new JIRA deployment I am not using sprints yet since the work is done and want to records the release content. Seems when I add the stories it adds Epic.
We do Versions as Versions. Epic's as major initiatives in a version and stories as parts of epics typically.
So, Lets take version 1.0.
That version will have a new tool called widgetnator. We'll create an epic for widgetnator.
To make widgetnator work, we need 3 stories that might have a ton of subtasks.
Stories might be - Design UI, Write the Code, Demo to team.
You might have tasks as part of the version. Tasks could be minor bug fixes, a tweak to a document, etc.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs