Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,993
Community Members
 
Community Events
168
Community Groups

Update 'Project' Field to Reassign An Idea to Another Discovery Project

Hello, 

 

Is there a way to 'edit' the Ideas 'Project' so that we can reassign an idea from one Product Management Discovery Project to another? 

Quite often, ideas are created, but once the initial assessment is done, we realise that the idea would be suited best in another Product Management team etc. 

I can't seem to find a way to edit an Idea, and reassign it. 

Does anyone know if this can be done? If so, how? 

Cheers,

Troy

2 answers

1 accepted

1 vote
Answer accepted

Hello Troy, 

Moving issues from a project to another isn't yet a feature in Jira Product Discovery, but there is two workaround to do from the search engine.

1. you search for the issue via the search bar, and click on the issue key. The issue view is a bit different from what you are used to, but using the three dots on the top right corner you are able to select "Move" and you can move it to another project

2. Still from the search screen, click the three dots on the top right corner, and then "bulk edit". It's useful if you want to move several issues in the same time to the same project. 

Move issues.png

Note that by moving issues between projects, insights are going to be lost as per Known limitations of Jira Product Discovery beta .

Cheers, 

Hermance

Hi @Troy Cope ,

You could either:

  1. Set up a JQL filter to show you all ideas created in X days and use the Bulk Manage feature to Move selected issues to the desired project, or,
  2. Create a new field to represent 'Project'
    • Create an automation
    • When Project Field is updated
      • If X, create new idea in Project X, copy over existing fields, delete/archive original idea(link to new idea)
      • If X, create new idea in Project Y, copy over existing fields, delete/archive original idea(link to new idea)
      • etc

I think I'd prefer option 1 in your use case. A little more manual but you are able to maintain more of an audit trail than with 2. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events