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
Next: Root
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.
If you have a story that was assigned to a user and completed, but then needs to be revised and the original user can't do it, do you:
If I do option #1 the reporting results are tainted and unaccurate
If I do option #2, the breadth of the new revisions are not accurately reflected via a subtask (i.e. the new fix isn't so simple and requires a lot of work)
If I do option #3, it appears we're creating 2 seperate deliverables when in reality it was just another version of the original story
Thanks Walter. This definitely makes sense. I appreciate all the time you took to write an answer.
We use a pretty unconvential way of organization for us because we work in marketing - not products. So our organizational structure is quite different than most. Here's how we break things down:
I still understand your meaning though and I'll think about it some more. My initial inclination is to go with #2 but don't reopen the Story (Deliverable) because that would mean the original assignee would then see it again in their dashboard.
This is a pretty big outlier issue for us, so no matter the outcome, this situation probably won't come back around for awhile.