I am not sure what "mark as done" does to an Epic.
Every time when I "resolve" an epic with resolution "DONE", and then "close" it. The epic can still be seen in the left-hand panel of Backlog view. I know that I need to click the button on its top-right corner and choose "Mark as Done".
I am confused about the design. I have resolved and closed the epic, but I still need additional step/operation to "mark as done" to make it disappear in the list of left-handle panel of the backlog.
How can I save this operation?
Thanks a lot.
For Epic issue types there are indeed two different statuses:
there are a number of threads that discuss the why's and wherefore's of this but basically an Epic can span multiple projects and there has historically been a need to have an independent "done" to complete a project independent of it's issue status in the project where it exists.
you might find this recent thread useful - set-epic-status-to-done-on-issue-ark-as-done
In fact, I can accept the design that epic has two types of status(es).
But what made me uncomfortable is that there is the only way to mark epic status to DONE, in the Backlog -> left-hand panel -> scroll and find the epic -> click the top-right -> click "mark as done".
In project management, it is really complicated to us to locate it and mark it as done.
I am not sure if we can do it when I close the epic, there is another option for us to choose "mark it as done“, etc.
I read the thread you mentioned and have not tried as importing an app into company JIRA system need a workflow and approval.
thanks a lot.
I agree with this. Worse even, if you try and do a search on 'epic status=done', it doesn't display the tickets, and when you try make the field display on a card/ticket, the value seems to be to choose (it has no value set, when wait, i thought i had just marked this as done in the Board view).
it seems to be related only to the 'epics report', which really doesn't tell you much, and i personally find useful.
to sum up:
1) having 2 status is addressing some niche edge business case, it would be much better to have a single status
2) the epic status feature fundamentally doesn't work, cannot be retrieved nor amended
As above, you need to add the custom field "epic status" then when you edit the epic you will have a drop down box that will allow you to change the epic status, which is different from the issue status (even though the issue is an epic), All seems a bit mad to me, but there you go.
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