This question is in reference to Atlassian Documentation: Creating project-specific releases
I have a new project added in my portfolio and I would like to sync it with an existing cross project releases with the rest of my portfolio projects. How I do this?
You can do this, just figured it out.
If I understand your question correctly, you've just added a new project to your plan and you want to add an existing cross-project release to that project. This is not possible as it is not how cross-project releases work.
Think of Cross-project releases as collections of releases that only exist within a plan. Thus, it's not possible to add a cross-project release to project; it's a one-way street. But you can a create a release in that project and add it to the cross-project release.
In your case, to achieve the desired effect you will need to create a new release in the freshly added project and add that to the desired cross-project release in your plan.
You can find out how to manage your cross-project releases on this page,
Hope that helps.
Hi Allard and thank you for your prompt response.
So, I was not clear. I have several CPR’s in my Portfolio and recently I have added a new project in my Portfolio. This new project didn’t have any releases defined and I wanted to add existing Portfolio CPR releases to this new project, so that we inline respective deliverables. I cannot find any relevant info on how to do this.
Think of Cross-project releases as collections of releases. They only exist within a plan.
Thus, it's not possible to add a cross-project release to a project; it's a one-way street. But you can a create a release in that project and add it to the cross-project release.
I've update my above answer to reflect this. Hope this helps.
I too have added a new project to a plan. I want the new project to be included in the cross-project releases that already exist in the plan.
One of the reasons we're evaluating Portfolio is to use cross-releases to syncronise releases in the plan across projects in Jira. We have many projects and it's more managable to add them to a plan one-by-one rather than all at once. This restriction blocks this more managed approach to building a plan.
My case was the same as the original post, and your answer is Portfolio can't do that. The link confirms that, so it does not solve my use case.
As it stands Portfolio can not bring new projects into a plan and use existing cross-project releases to synchronise their schedules.
So, the answer is not to create a new issue, but to suggest a change: https://jira.atlassian.com/browse/JPOCLOUD-1927
I think the confusion comes because when a new CPR is created all the projects in the plan get their own specific release automatically without having to manually add individual releases to each project
However, this automatic behavior cannot be replicated when adding a project to a plan *after* the CPRs have already been created.
I think it is a new feature request :)
I have the same use case. I 'think' the only way to do it is to delete the XPR release (in portfolio and all projects), then re-add it and include the new project.
I don't understand why
1. it makes sense to add the XPR release to all projects included when it is created,
but not allow sharing the XPR release to new projects added to the plan.
2. why the XPR releases added to the products included at creation time are 'copies',
such that if you update the Porfolio XPR, it doesn't update the 'copy' in each project.
...again, I think you have to delete the XPR and recreate it to properly share the update.
This use case is common for us. We have a number of large projects that have to be delivered as part of a tool kit, which has milestones, all of which can shift. Portfolio seems like the perfect tool to manage this, but the XPRs don't provide this functionality. We'd prefer the 'one-way street' that goes the other way, although a two-way street would be best.
Indeed in the URL above Allard posted you can find the way how to do this, add a new project to existing CPR.
However, Portfolio for Jira didn’t work for me and finally after many months of trying to work with it, we gave up. Simply, the way it has been implemented and its philosophy is not what could be really useful (even thou, it looks like this). Last but not least, it has lot of problems.
Instead of Portfolio, try to utilize Epics. I believe you can achieve what you need and sync across different projects.
Hi Atlassian Community, My name is Avni Barman, and I am a Product Manager on the Confluence Cloud team. Based on feedback from you, we are giving admins more power to create templates that a...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events