Our project is configured to use Rapid scrum boards with our own workflow which does not allow all transitions to occur.
We are using stories and sub tasks (and soon we will be using epics as well). The stories are used to indicate a certain (large) feature. Which will be broken down in to sub-tasks.
These subtasks will be istimated and as of now, the total time is assigned to the story as original time and the remaining time for the story is set to 0.
Work is logged against the subtasks and this makes sure for a 'nice' burndown chart. The problem that we are facing though that in the 'plan' view the "open issue"-value remains quite high (total amount of stories original estimates that are still 'open').
Our stories stay opened untill all the subtasks are done. Then and only then the story is moved to Done (using the Done buttin in the rapid view) (using swimlanes based on stories).
What would be a better way to handle this? This leaves for a biased indication of work not started/work in progress and work done.
Did you try to use Epic Issue Type to act as a large body works? You can try the flow below:
Epic -> User Story (sub-tasks)
You may avoid the subtask to be stay opened and not able to complete the user story. Hope it helps.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
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