Separate project to manage initiatives in Portfolio

In the Getting Started page on how to orgainize issues sources, it mentioned

"If you plan to use a custom hierarchy such as initiatives we recommend you create a separate project and store those issues independently. In that project configure the issue types and, if you do not already have one, create an issue type for your custom hierarchy issue type. If you’re not using a custom hierarchy, you can skip to step 3."

Are there any solid reasons to use a separate project to track Initiatives independently? Are there any drawbacks to have one single project to manage all issue types including Initiatives? What are the pros and cons? 

Thanks in advance.

 

 

1 answer

0 vote

Very often you will want your initiative (or program or portfolio) level issues to be visible to a separate and maybe limited set of people.

There might be an ideation or approval lifecycle process behind the issues and you might only want to release them to be actually worked on after approval. Keeping them in a separate project saves you a lot of hassle in managing visibility and/or access to them.

You also avoid that people by accident start creating issues of the wrong type in your operational project, which clutters your overview of a strategically important piece of information.

So it's really just a best practices thing, making things easier to manage.

Hi Walter,

When you say "separate project" am I correct that you mean creating all Portfolio custom issue types/initiatives in a SINGLE project in JIRA?

Thank you for the clarification!

Kelley

Exactly!

Hi Walter,

How to relate these independent Initiatives to lower Epics in (other) projects?

The whole idea of having Initiatives separately configured in a separate project is to hide them in a way for users which do not know anything about it.. I agree...

But in case you want to use this Initiative issue type for e.g. Portfolio, the relationship with Epics and indirect also Story's is very important to get a release calculation.

Hi @Nico Paffen,

Definitely. In your Portfolio plan, make sure you import both your initiatives (use the project as issue source) and the rest of your backlog (preferably use a board as your issue source).

Filter your scope view to Epic level and make the Initiative column visible. Then simply map your Epics to the Initiatives they belong to.

Suggest an answer

Log in or Join to answer
Community showcase
Josh Frank
Posted Dec 01, 2017 in Portfolio for Jira

Portfolio for Jira: Share your tips!

The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag.  Do you structure your teams i...

564 views 6 8
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot