Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Moving a ticket from one project to another

Deleted user
May 14, 2022

We have two projects:

  1. One contains an ideation/prioritization Kanban board that readies a PRD and has a limited audience
  2. the second also has a Kanban board but for the actual PRD review from the larger company before it's taken up for actual development.

I'm trying to export a task from the last column of board 1 ('ready for review') to the first column of board 2 ('to do') but it comes up only under 'other issues' and shows already done. I've discovered this is because there has to be at least one 'done' status. As a workaround, I've added a dummy column on the board and set its category as 'Done' using the workflow editor. Now I'll move an issue from the penultimate column (one before the dummy) into board 2. 

Is this the best way?

1 answer

1 accepted

4 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 15, 2022

Hi @[deleted] 

First thing, I personally do not believe there is a "best" way to address this use case/flow.  Any way you choose to solve this with Jira will have advantages/challenges to address.  How you choose to solve this greatly depends on how your teams want to work.

A few ways I have seen this done are:

  • Two issues
    • When your "idea" progresses to ready for development, let it move to done and then clone it before moving it to the new project.
    • This can be automated a bit with an Automation for Jira rule, particularly if you have two "done" status values for your ideation/prioritization board: done and abandoned, where only the done items progress to development
  • One issue
    • A variation of above, where the "done" issues get moved and then transitioned to the delivery/"backlog status" after completing ideation/prioritization
  • Multiple issues (multi-level Kanban to span more of the value stream flow)
    • Create issue types for ideas, and they only live on the ideation/prioritization Kanban
    • Modify the ideation/prioritization flow so it includes "building" and "confirming learning", where ideas spawn new work items in the development flow (other projects) when moved to building, and where results/learning can be performed after delivery
    • This helps better see the overall progress of ideas and capacity of the value stream

Kind regards,
Bill

Deleted user
May 16, 2022

Thank you very much for the pointers, Bill. Let me try these out and see how it works out!

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events