Hi Would like to know,
Is there a way to reveal/ have visibility over an issue which is partially done /withdraw/ completely done ?
Sometimes there are situations an issue is partially done and withdrawn, the team will move them to 'Done' status in the work scheme, but I want a clear visibility to know they are not completely done, but partially or withdrawn.
Is there a way I can reconfigure to reflect this?
Yes, this is what I have been thinking: Now my workflow is ' To do- In Progress- Done', I can add two more statuses which are ' To do- In Progress- Withdrawn- Partially Done- Done', but I do not want to complicate things, especially not so many issues are withdrawn.
If there is some other ways to know when an issue has moved to 'done' because it is withdrawn but not because it is actually done/resolved, it will be great.
And I want to know when an issue is not 100% complete, but 50% or 70% or 80% complete, it will be helpful to give me more visibility. I understand issues like this can stay in 'In Progress', but they are partially done.
Just wondering whether some other projects have the same concern...
Hi @Christina Liang , You could define 'withdrawn' as a resolution ( this document describes how https://support.atlassian.com/jira-cloud-administration/docs/configure-statuses-resolutions-and-priorities/), as well as 'done' and others like 'duplicate' and 'won't fix' (if the decision is not to fix). Then your workflow could have the statuses 'To do', 'In progress', 'done' and 'closed'. Tickets move to 'closed' status only when they have been completed (100% done and reviewed) and then the resolution gets set (to either 'done', 'withdrawn', 'duplicate', 'won't fix')
For the % , you could have a custom field with a drop down list of values (0, 20, 40 60, 80, 100) to indicate what percentage is completed, and let the team members (or the scrum master or the product owner) update the value accordingly (maybe during standup, or offline, or during a team sync-up).
We use 3 different statuses for Done - really 4.
Done is when the issue/work was completed and deployed.
If the work has not started yet and we decide to "withdraw" it - we use the status of Discarded.
If the work was already started and we decide to stop it for now and MAY return to it later (or not) then we use Abandoned status.
If the work was already started and we decide to stop it for good - meaning we are never going to complete it, then we use the Aborted status.
Here is blog from my boss that has more information:
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events