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
It is understood that it is not best practice to create stories which are not independently testable. Unfortunately, my team tends to create Stories which must be all be completed in order for code to deploy, and QA to commence. Additionally, there is an expectation that when an item hits the "awaiting deployment to QA" column, that QA then request the deployment. However, because there are dependencies between stories, it is a challenge for QA to know, without a lot of manual steps, when all the pieces are ready?
We have discussed yet another column, or adding an additional link type, prerequisite or dependency, or similar. Then potentially we can automate the movement of the work item to the next status when all stories share the same defined status. What is the best way to manage this dilemma using Jira?
Thoughts? Best practices? Reading references?
I'd consider some things here...
^ I think I'd look at these two first, before looking at an automation rule, or more statuses, etc.
What do you think?