It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Portfolio Plan Features - Move between plans

How do you move a feature between plans?  I'd like to have a master feature plan and then move features to plans used for project execution at a later date.

1 answer

0 votes

Hi Dan,

The plan is going to include issues from the issue sources by either Project, Filter, or Board, so looking at how issues are tied to these items would be the method of moving to a new plan. Noting using a Board as the source is the only way to include sprint data in a plan.

So looking at a project, you can directly move an issue from one project to another as covered here:

Moving issues from one project to another can also move an issue by the filter, However looking at the other two, a board and a filter are both based on the filter, one is a direct filter set in the plan the other is the filter used by the board.  Filters are views of lists of issues, they don't hold any issues really but are rather rules and criteria to be included. To "move" an issue, you change the filter to include the desired issues.

So using Boards as an example you could create your new board, and make sure it includes the issues you want to "move" as they meet the speciffic criteria of the filter. Then go to the existing board, and change the filter so it no longer includes the issues one that criteria is met.

A simplified example would be to have Board one with a filter of "project in (a,b,c) AND status in (status1,status2,status3)"  and then board 2 has a filter of "project in (a,b,c) AND status in (status4,status5,status6)" this way when the issues are transitioned from status 3 to status 4 they will no longer be in board one and will show up in board 2.  This is pretty straight forward on kanban boards but if you are suing scrum this too does inherit some draw backs if your using a sprint across multiple boards like what is described here.

Another approach is to have a workflow where when an issue reaches a certain point of completion you can have a process to create a new issue manually as part of the criteria for being complete for phase two EXE design team is done and part of marking an issue complete is that a development request is created on the internal processes, or look at add-on app to automate the create it in a secondary project such as "Add Issue on Transition for Jira Cloud" OR "Automation for Jira"

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

303 views 1 3
Join discussion

Community Events

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

Events near you