If Story is small enough we estimate it, but if it is too big, we split it to Task (we do not use sub-tasks) and estimate Tasks. How can I easily know/show that this task is for specific Story? It is sometimes problem when we have the very similar tasks (or even the same) for 2 different Stories. Also I think that backlogs (Sprint and Product) would be much more tidy and readable. Can You help mi with this? Any ideas?
The problem when you split things is that there's no logical tie between them - you don't know the difference between a split and a few issues that have been created together.
What I would do is promote the story to an Epic and then break it down into smaller stories and tasks.
Another option would be to link the issues together with issue links, but that's not really going to relate them together unless a user looks at them in full.
I don't understand the "more tidy and readable backlogs" - more than what? And how would you do it?
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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