When a copy is made of a jira plan, it also copies the releases

[Bruijn A_ de _Aron_]

Hi all,

Recently we've hired an external company that set up a new way of working for Jira within our company. They've made some roadmaps (plans) where releases are shown in the timeline. The releases show multiple spaces which is fine because they work together. My problem begins when I make a copy of that roadmap and change the "work in your plan" to different spaces with removing the old spaces. The releases then show me the spaces of the roadmap I made a copy of and the new spaces I added. I can remove a single release by clicking on the 3 dots by the end of each release which deletes the release from the plan, but if that same space makes a new release it shows up in my new plan. 

I have no option to exclude a space from my plan which seems like the solution for me. Hope the story is clear and someone has a solution. 

[Dmytro Rudenko _ Release Management · Accepted solution]

Hi @Bruijn A_ de _Aron_ ,

In Plans, issue sources and release scope are two separate things. Removing spaces from "work in your plan" doesn't drop the releases tied to them. Those are scoped separately.

In your Plan, open the Releases view from the left navigation. There should be a full list of versions currently scoped into the plan. Untick the old-space ones from there, not through the 3-dot menu on the timeline, that usually only hides, doesn't unscope.

If there are cross-space releases in the list, those are linked to the plan directly and survive any source change - you have to remove them explicitly as well.

The "new release from old space still appears" part is the bit I'd dig into: that usually means the old space is still referenced somewhere, through a board or filter source you might've missed, or through a cross-space release pulling it back in.

Quick question: when you removed the old spaces, did you take them out from the full issue-sources list, or just untoggled some boards? That distinction matters here.

Cheers

[Bruijn A_ de _Aron_]

Thanks, this was the solution! I had a board filter which referred to other categories via "category in (...)". This made the other spaces show up in the roadmap. There were no cross-space releases used in this instance. 

[Dmytro Rudenko _ Release Management]

Yeah, that was a sneaky one. Board filter sources are easy to miss in Plans.

Side note: when cross-space release coordination becomes a regular thing, native Plans gets brittle.

Disclosure: I'm with the team behind Release Management for Jira, which adds cross-space release packages and automated release notes on top of Jira versions. Worth knowing if that pattern grows.

[Tomislav Tobijas]

Hi @Bruijn A_ de _Aron_ ,

With the following:

...but if that same space makes a new release it shows up in my new plan...

Are you saying that even if you change plan source and 'remove' all releases from previous source(s) (meaning, spaces), whenever a new release is added to that 'old' space, it will also show in your new plan? 👀

Also, do you have cross-space releases or only single-space releases displayed in that plan, which you're duplicating?

Btw, have you tried reaching out to Atlassian Support to see if they can help you troubleshoot this? Their team can view your data (if you permit them) and check the behavior from the backend perspective as well.

Cheers,
Tobi