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; } } }

Visual Progress

Cornel Simons

Hi,

We have a question about the timeline in plans (Jira). As can be seen in Figure 1, there is no visual progress is shown, while there is progress in the underlying tasks of these Epics.

For example at Epic: "Salesforce - KD - bulk beantwoorden van klachten" in figure 2 you can see the progress of the underlying tasks with a visual representation, we also expected this in the column “voortgang (aantal issues)" figure 1 but unfortunately we are unable to display the visual progress.

Can you help us with a solution?

Schermafbeelding 2024-07-24 om 14.16.40.png

Schermafbeelding 2024-07-24 om 14.17.19.png

Accepted answers

Hans Polder_7ci2ta

Hi @Cornel Simons ,

This is because the child issues don't seem to be included in the Plan . You can also see this by the lack of the > expand icon in front of the Epics in your screenshot.

You will need to add issue sources to your plan to also include the children of these tickets, then it should work!

Screenshot 2024-07-24 151845.png

Cornel Simons

@Hans Polder

Hi Thanks for your quick response, what do you mean by add issue sources? thwy are linked see screenshot: Schermafbeelding 2024-07-24 om 16.19.00.png they are linked

All comments

Hans Polder_7ci2ta

Hi @Cornel Simons ,

This is because the child issues don't seem to be included in the Plan . You can also see this by the lack of the > expand icon in front of the Epics in your screenshot.

You will need to add issue sources to your plan to also include the children of these tickets, then it should work!

Screenshot 2024-07-24 151845.png

Cornel Simons

@Hans Polder

Hi Thanks for your quick response, what do you mean by add issue sources? thwy are linked see screenshot: Schermafbeelding 2024-07-24 om 16.19.00.png they are linked

Hans Polder_7ci2ta

Hey @Cornel Simons ,

Please check the steps below:

1. In your Plan, click 'Plan Settings' on the left.

Screenshot 2024-07-24 162949.png

2. Then, choose "Issue Sources" on the left, and observe the information on the right.
Screenshot 2024-07-24 163111.png

ONLY the issues in the scopes of the items on the right, will be shown in the plan. So in my test environment, that would mean anything that is part of the filter that is used for the 'MOBL Cowboys' board, and anything in the 'Marketing Content' project.

In your case, you'll likely find one or two filters listed here, where the filter only contains the Epics (or at least not the places where the children might be).

So, you should either expand the filter that you're currently using, or add a new filter that includes the places where your Epic's children reside.

If you need more help, please reply here with some screenshots of your Issue Sources setup, and the details/filters of the boards/filters/projects that are in the scope.

Cornel Simons

@Hans Polder

Yes, it worked, thank you very much for your quick help

Hans Polder_7ci2ta

Cornel,

Graag gedaan! Om anderen te helpen, kan je op de 'Accept Answer' knop klikken van mijn antwoord? Dat markeert de thread als 'opgelost' en laat zien wat de oplossing is voor anderen.

Max Mykhailenko

Hey @Cornel Simons ,

If you’re looking for a visual way to track Epic progress, you might want to check out Focus Flow! 🚀

It shows progress not just as a percentage but also visualizes effort distribution over time, helping to spot where work is actually happening. This can be really useful when an Epic has a lot of underlying tasks, but progress isn’t immediately clear in standard Jira views.

Right now, Focus Flow provides this as a separate screen, but if it’s helpful for your use case, I’d be happy to explore ways to integrate it further!

Check it out here:

🔗 Focus Flow on Atlassian Marketplace

Would love to hear your thoughts! 😊

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud