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
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
What are the best practices regarding closing an epic vs. resolving one?
We have a company-managed project, wherein issues’ final status is “deployed” with resolution “done.” The options for completed epics are “resolved” or “closed.”
I would argue that that depends on how you are using epics.
In terms of resolution (resolved vs closed) on an epic - I am not sure if that matters structurally to Jira beyond the reporting aspects. You could use those two terms to differentiate between epics which did not make it into production (resolved) vs those that were successfully deployed (closed). Or, and better, use as Bansal suggests.
I will point out that marking an epic as Done within the Backlog Epic listing, which is not the same as marking the resolution of the epic as Done (unless Atlassian fixed this and I missed it), can prevent Jira from showing that epic as an assignable epic link when linking issues to epics. This prevents your users from assigning issues to epics that are completed. That can be done by navigating as shown here:
No idea. I wonder if this functionality is actually an abandoned artifact from before the resolution functionality was incorporated. That might explain why the interface to reach it is in the backlog.
The lack of integration between the Mark As Done in the Backlog and Set Resolution: Done in the workflows could also fall under JIRA's general lack of out-of-the-box functionality about handling parent-type issuetypes (simplistic workflows that don't really do anything).
Your guess is as good as mine!
No, I believe resolution is older. Most of the screens currently considered mainline Jira functionality like kanban boards and the agile backlog actually stem from a time when they were part of a plug-in called greenhopper, back when dashboards were the primary interface. So probably this is just a rudimentary function. Still, watching out for this thread, really interested in what useful flows people found for this :)
Abel, it was the multiple ways of marking an epic as done that sent me down this path. I'm glad to see others are puzzled by that setup.
To answer your question, they are specific instances of feature changes, with a couple of exceptions. We started this Jira instance at the same time as the project, and are moving into maintain/improve mode.
I agree that Bansal's suggestion is a good use.
Hi @Kelly Arrey
The "Mark as Done' sets the Epic Status, which then also allows the epics to vanish from drop-down lists...rather than cluttering them up.
We use an automation rule to set it, similar to what you are doing with the workflow post-function on transition.
Here is my best practice:
I believe this is also what Atlassian teaches in their trainings. The reason is that some functionality I can't recall at the moment rely on the resolution.
I also try to use epics to represent a feature that is meant to be implemented in a given time period. This makes the roadmap feature in Jira SW Cloud Premium so much more useful.
My criteria for a feature are:
It is a matter of taste. Generally speaking Resolved means that all works are done and Closed means that manager is happy with resolution and Epic is no longer needed.
A rule of a thumb: if you ever searched for closed epics, you need Closed. Otherwise Resolved is enough.
Our practice is, we need to ensure all the Stories in the Epic are completed (Done), and once Done, we are Closing the Epic as well if those Stories linked to Epic are satisfied. But if the Epic is much broader, like stories keep on adding, We are keeping it to In Progress.
For work tracking in Software Projects, we are focusing Epics on a time bound set of Stories or Tasks that are related at a visual management/sponsor level. This lines up well with Roadmaps and Plans. Therefore Epics are Closed/Done/Completed based on our usage and there is no need for 'Resolution'.
I would say Both? You moved it to a Closed status but then set the resolution to Done. Just like you do with tasks or stories or whatever - they move to a Done status but you also set the Resolution to Done.
Recommended Learning For You
Level up your skills with Atlassian learning
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Managing Permissions in Jira Cloud
Sharpen your skills at configuring and troubleshooting permissions in Jira Cloud with this free course.