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

In Advanced Roadmaps whenever I create an initiative in one plan, it shows up in all the other plans

Ng, Alberto

Whenever I create an initiative in one plan, that same initiative is mapped to all the plans in my organization. I have to then manually remove that initiative for each plan which is very time consuming. And, it gets worse as I have multiple folks creating initiatives across multiple plans.

Is there a way to stop having a new initiative show up in all the plans? I just wanted it to live in the plan where I created it.

Accepted answers

Ste Wright

Hi @Ng, Alberto

To confirm:

The "Initiative" is an issue type, configured in the hierarchy above an Epic (or similar)
You're adding the Initiative to a Plan and then...
Committed the change to Jira

---------------------

If this is correct - then the Initiative will show up in any plan where it is configured to do so.

Plans visualise the data available from its Issue Sources. If two plans share the same Issue Source, then when an Initiative is created/committed from one, it will show up in the other.

If you create the Initiative and don't commit the change, it should not show up in any other plan. It also won't be available in Jira though - so unless it's just for scenario planning, this would be counter-productive.

You'd need to refine the Issue Sources that each plan's data is received from to avoid this scenario - do this via: Plan Settings (cog icon) > Configure > Issue Sources.

---------------------

Let us know if this works for you - if not - or you need help with configuring your Issue Sources - please provide us some more specifics about your scenario so we can help you further

Ste

All comments

Prince Nyeche - ELFAPP

Hi @Ng, Alberto

That's because you have an Initiative configure in your Hierarchy configuration, so it will be available on all Plans created. So you can't simply configure it and not have it show up.

Ste Wright

Hi @Ng, Alberto

To confirm:

The "Initiative" is an issue type, configured in the hierarchy above an Epic (or similar)
You're adding the Initiative to a Plan and then...
Committed the change to Jira

---------------------

If this is correct - then the Initiative will show up in any plan where it is configured to do so.

Plans visualise the data available from its Issue Sources. If two plans share the same Issue Source, then when an Initiative is created/committed from one, it will show up in the other.

You'd need to refine the Issue Sources that each plan's data is received from to avoid this scenario - do this via: Plan Settings (cog icon) > Configure > Issue Sources.

---------------------

Let us know if this works for you - if not - or you need help with configuring your Issue Sources - please provide us some more specifics about your scenario so we can help you further

Ste

Ng, Alberto

Thank you, I understand where I went wrong!

The setup that you mentioned is correct. I also have one JIRA project holding all my initiatives which became the project source to all the plans. And, this is the problem which you helped me identify.

Whenever I create a plan, I add the same project and then create initiatives within that project so that any plan using the source project also inherits the new initiative, and shows up in there.

So it looks like I have to create multiple JIRA projects to separate the initiatives. Then when I create an initiative I'll use the appropriate JIRA project(s) so that it only impacts the appropriate plans.

Would this be the right way to go?

Ste Wright

Hi @Ng, Alberto

That is one option which will work.

Your other option is to use boards / filters to limit your source data.

For example, you could keep all your Initiatives in one project but group them using components. Then create filters per component, applying these filters as each plan's Issue Sources.

I would test both options - taking into account what other project configuration is applied to the Initiatives now - and see what feels the best for your teams

Ste

Ng, Alberto

Hi @Ste Wright

I tried the filter option, and it gives me more flexibility. I like it!

Thanks again for the suggestion. It made a difference.

Best,
Al

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

advanced-roadmaps