Can I create a totally separate plan for the same projects/initiatives/epics?

What would happen? Where would there be conflicts?

 

Update based on follow-up questions:

So the situation I have is that one area of our organisation is using the portfolio plugin to get a high level view across multiple release teams. They don't really intend to push back changes to our project, but need us to keep our estimates, epics and intiiatives up to date so that they can manage plans across the portfolio and identify areas for optimisation. Conceptitually in portfolio they are doing a couple of speific things:

-They use "Teams" to identify entire release teams, not individual scrum teams

-They use "Themes" to identify funding sources, not strategic themes.

 

In order for portfolio to be useful to me and my project, I believe I need my own plan where:

-I can use "Teams" to identify individual scrum teams for allocation of work across the scrum teams and work out when a scrum team is over/under capacity or can't hit a release date.

-I can use "Themes" to tag the strategic themes / goals of the platform we work on.

 

So I guess them my questions might be:

-Can you have an epic that's in two plans, and has to separate team and theme models assigned to it.

-If I update a shared epic in one of the plans or in the proejct  directly, will the other plan be able to pull that update without issue?

1 answer

Can you elaborate on this more? Where does JIRA comes to play here?

Hey Gabrielle! So the situation I have is that one area of our organisation is using the portfolio plugin to get a high level view across multiple release teams. They don't really intend to push back changes to our project, but need us to keep our estimates, epics and intiiatives up to date so that they can manage plans across the portfolio and identify areas for optimisation. Conceptitually in portfolio they are doing a couple of speific things:

-They use "Teams" to identify entire release teams, not individual scrum teams

-They use "Themes" to identify funding sources, not strategic themes.

 

In order for portfolio to be useful to me and my project, I believe I need my own plan where:

-I can use "Teams" to identify individual scrum teams for allocation of work across the scrum teams and work out when a scrum team is over/under capacity or can't hit a release date.

-I can use "Themes" to tag the strategic themes / goals of the platform we work on.

 

So I guess them my questions might be:

-Can you have an epic that's in two plans, and has to separate team and theme models assigned to it.

-If I update a shared epic in one of the plans or in the proejct  directly, will the other plan be able to pull that update without issue?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,807 views 18 22
Read article

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