nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

'Progress (issue count)' field not counting issues properly

I have many epics with sub-issues (tasks, bugs, stories) that are not being displayed in the 'Progress (issue count)' field at all.

Here's an example of an epic whose sub-issues are not being displayed in the progress (issue count) field at all.

To be fair, it's 189 sub-issues. Is there a limit to have many issues in an epic is supported by the 'Progress (issue count)' field?

If not, how can I create a custom field that does take all epic sub-issues into account? (so what this field is supposed to do, but actually do it)

Using Atlassian Jira Project Management Software (v9.4.4)

Comments

Joseph Chung Yin

@JA -

Hi JA:

For those EPICs in question, the a few things that you should check first are:

Issue Sources - To ensure you are bringing the child issues into your plan from all related projects.
Exclusion rules - To ensure you are not excluding issues by accident.
Removed issues - To ensure you (or other plan editors) didn't removed any issues.

Here is a reference link on AR for Jira - https://support.atlassian.com/jira-software-cloud/docs/set-up-advanced-roadmaps-and-change-plan-settings/

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Yep, that did it. Thank you so much!

For others who might find this in the future: In issue sources I was including boards of different projects, but for the problematic one that didn't include sub-issues, I was including a filter for a few selected epics of interest (with a given label). So I created another filter for the children of those selected epics. And voilà, problem solved.

Much appreciated.

This JQL filter that gets all epics of a given label and their respective children issues:

(Type=Epic and labels=YOURLABEL) OR issueFunction in issuesInEpics("Type=Epic and labels=YOURLABEL")

And then I add that filter in the issue sources on the advance roadmap plan

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

jira-software-cloud

jira-software-server

advanced-roadmaps