Move bulk tickets from Discovery Project to Software Project while preserving fields

[Brooke Smither]

Situation: I am moving bulk tickets from a Discovery Project board to a Software Project board. 

Background:

• We are working on Product development.
• The board fields are aligned.
• Permissions are open.
• I edited the Software project issue type fields within this particular issue type to align with the Discovery project fields. 

Assessment:

• During testing, when I moved a single ticket from the Discovery project to the Software Project Board, I lost all my fields—nothing came over beyond the first few words of the description.

Request:  What could be going on here?  

[Robert Tang · Accepted solution]

Double check the fields you have in your Discovery project are Jira fields and not only Discovery fields as your software project isn't seeing the Discovery fields (or check the custom field IDs to see if they match in a discovery ticket/project and a software to verify they are different).  That may answer why the field values don't copy down. In your Discovery project, you can also go to Project Settings -> Fields -> Add Global field to see Discovery or Jira fields.  If you plan to have Ideas cascade down to a Software project, it may be better to use Jira fields.  

You can also try Automation to copy the field values when moved to a software project.  I had a project that once it hit an Implement state in the Discovery project, it auto created a ticket in a software project and copied those values to new fields.  

[Brooke Smither]

Thank you, Kevin!  After reviewing the Discovery project this morning, this is my issue: the original build did not utilize Jira global fields. 

I've already created custom global fields in Jira for the software project board...

Is there a way to change the Discovery field to a Global field within the Discovery project?

Context: I have a data team constantly working on adding variables to a product. They used a Discovery board to put the " feature wish list" of internal and external stakeholders. They now want to move this work into the Software project to begin working faster, and with Gantt - they've realized the table format is not sustainable. 

We have three years of 'backlog' ~260 tickets that need to be transferred without losing the critical criteria contained therein.  

Could you share the automation you use?  They do move tickets from one Software Project Board (A = development) to Software Project (B= build).

[ArulAnthonySebastian Nadar]

Please check the source projects field configured. 

Workflow with any post function changing custom field. 

So that all the field can retain its value.