In the new Jira issue view, how do I differentiate Epics open vs closed in the Epic Link field?

[toni.d]

Currently, in the new Jira issue view, there's nothing to differentiate open vs closed Epics in the Epic Link and it's providing a list of Epic options from across our entire instance of Jira, not for Epics contained with the related project. I've attempted to look at the new issue layout config, fields config, and other project settings. Is there a way to configure this in the new Jira view?

Also, in the old Jira issue view, it provided many options...Suggestions, which seemed to be specific to the related project; All epics, which seemed to be from our entire instance of Jira...and the option to 'Show done epics'.

[Earl McCutcheon]

Hi Toni,

When you're looking at an epic on a Next-Gen project, then moving the Epic to final status used by the project board will add a green checkbox to the epic on the roadmap view as an indicator it is completed and it will no longer be available in the "Add to Parent issue" list on the other issue types.

When you're on a Classic Projects even if the Epic issue is in a "DONE" status with a resolution set, it will show up in the Epics panel and when present in the panel will be selectable as an epic link until flagged with an additional "mark as done" step to remove it from the Epics panel in Backlog, you have to go to the Epic and there's a dropdown next to the name of the Epic and select the  "Mark as Done" option here:

Regards,
Earl

[toni.d]

Thanks Earl. The "DONE" status makes sense, but what about the Epic Link field showing me all Epics across all projects? ...I only want to see Epics for my project.

[Earl McCutcheon]

Hi Toni,

Happy to help out so far, and for the Epic Link field there is an intended level of cross over between projects, Check out THIS COMMENT on the Feature Request related to this functionality, describing how the Feature was implemented to allow more restriction to the available choices adding in a Show open epics only option or a Show open and done epics option, but overall the intended functionality of the system is to be able to link to an epic in another project for cross project workloads which are a base element of epics which often encompass multiple teams, on multiple projects, and can even be tracked on multiple boards. as covered in this Blog post going into more detail "Agile Epics: Definition, Examples, & Templates"

Regards,
Earl