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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We've started to use JIRA within our company and we've tried to keep things as simple as possible. What is causing us some pain is with the management of post-live testing tasks.
Our current process is simplified as:
We have user-stories with sub-tasks of: build, code review, test & post-live testing.
The issue that we have with approach is that we can't mark all sub-tasks as done because the story needs to be released to live prior to starting the post-live testing sub-task.
I appreciate that we could release user-stories that aren't fully done, however, I don't like the idea of doing this from a reporting perspective.
Is it better to have the Post-Live Testing task as a separate user-story/task linked to the user-stories that have been released?
How do you manage post-live testing tasks within your projects?
Depends on the severity of the bug, we would try to raise bugs and prioritise for the next release where possible.
It really depends on your team's definition of done of a story. If you are releasing to prod then I am more inclined to keep it as a separate story.