nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Losing custom field data when using 'Move' to change Issue Type

Jenn Molyneaux

Hello!

I've found a dozen or so articles about this issue BUT they all pertain to moving Issue Types between a Classic project to a Next-gen project. Unfortunately for me, that's not the case here. This is all happening within one project.

I've got a custom field within my Bug Issue Type named, 'Bug Description' (so that we can use default text to include a template for that field since you can't put default text into the System Description field).

When a user determines that Bug isn't the right Issue Type and they 'Move' it to a User Story, they're never prompted to map the contents of 'Bug Description' to something else within the User Story Issue Type and the data is lost.

Steps to reproduce -

Create a Bug and enter data into 'Bug Description'

Select 'Move' and leave the project the same but change the Issue Type from Bug to User Story.

At this point, finish the process and move the Issue. I'm never prompted to select a mapping for 'Bug Description' to anything within the User Story Issue Type.

Am I doing something wrong? Is there a way to make sure that the contents of 'Bug Description' are migrated into a field (ideally, Description) that exists within the User Story Issue Type?

Accepted answers

Mikael Sandberg

The data is not lost, it is just hidden. If you add the Bug description to the screen used by your user story you should be able to see it again.

All comments

Mikael Sandberg

The data is not lost, it is just hidden. If you add the Bug description to the screen used by your user story you should be able to see it again.

Mikael Sandberg

And if you want to move the information in Bug description to Description when you move an issue you can do that using automation.

Jenn Molyneaux

Hi Mikael -

Thanks so much for clarifying. I'm glad I haven't lost the data. That being said, I don't want to add the Bug Description field to the User Story Issue Type but Automation does sound promising. Would you point me in the direction of some documentation/articles on automating this when an item is moved from one Issue Type to another?

Mikael Sandberg

The automation template library is a good start, Jira automation template library, and it has a playground where you can set up an automation. And you can find the documentation here, Automate your Jira Cloud processes and workflows.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud