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

URGENT! EPIC special board

Dionei Piazza

Hi friends!

I need to create an epic board. This board will have 3 columns (NOW | LATER | FUTURE).

In the NOW column, it will show the epics that already have an issue started (in progress).

In the LATER column, it will show the epics whose issues are already created but not started (in backlog).

In the FUTURE column, it will show the epics whose issues have already been completed (done).

Any suggestions on how I can create this board?

Accepted answers

Trudy P Claspill

Hello Dionei,

You will not be able to create an agile board that shows Epic type issues based on the status of their child issues. The functionality of an agile board is to display the issues in columns based on the status of those issues themselves.

I think that the only way you can do this is to automate the update of the status of the Epic issue based on changes to the status of the child issues. An appropriate Automation Rule could be constructed to do that.

If your child issues and your Epic issues share the same statuses, then you would create a rule that looks like this:

(Caveat - I have not actually executed this rule in my environment, so I can't guarantee that it works)

Screen Shot 2020-06-09 at 6.29.14 PM.png

You would probably want to activate that rule only for the affected project. If there is more than one, be aware that the Standard plan for JIRA has a limit on how many rule executions can happen in a month for rules that apply to more than one project.

Here is a link to the Atlassian documentation for the above feature:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

If your child issues and your Epic issues use different statuses, then it is more complicated.

Hope that helps.

All comments

Trudy P Claspill

Hello Dionei,

If your child issues and your Epic issues share the same statuses, then you would create a rule that looks like this:

(Caveat - I have not actually executed this rule in my environment, so I can't guarantee that it works)

Screen Shot 2020-06-09 at 6.29.14 PM.png

Here is a link to the Atlassian documentation for the above feature:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

If your child issues and your Epic issues use different statuses, then it is more complicated.

Hope that helps.

Dionei Piazza

Hi @Trudy P Claspill

Greate! Sounds good!

Thank you!

Trudy P Claspill

You're welcome.

Upon reflection, I think there will need to be a bit more sophistication in the rule. Since you have the conditions of

NOW - any child issue is in progress

FUTURE - all child issues are completed

you would need to make the rule a bit more sophisticated so that the Epic would not move to FUTURE until all the child issues are done. The basic rule I presented would move the Epic to FUTURE when any of the child issues are set done. Similarly, if a child issue changed from In Progress back to To Do, you wouldn't want the Epic moved back to LATER unless all the child issues were set to To Do.

You'll have to invest a bit of time in figuring out how to implement that.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

board

epic