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; } } }

Asking to update Description field when migrating to a new Project

Abby O_Connell

Hello! I am migrating over 300 stories from one project to another. In Step 3 of the Bulk Operation process, it asks to update the "Description" field. Underneath the "Field Value" column is a blank box, but most of our stories have content in the Description.

Whether or not I click the box under "Retain," an error comes up that says "Description is required." If I put something inside the blank box, will it replace the Descriptions that are currently on the stories? I want to make sure we do not lose that content.

I did try to complete the migration with one Test story and was not ask to update the "Description" field, so it was completed successfully.

Any help would be appreciated! Screenshot 2023-07-11 at 3.48.28 PM.png

Accepted answers

All comments

Trudy P Claspill

Hello @Abby O_Connell

If any of the issues you have selected for bulk move have a blank Description field and the destination project requires the Description field then you will get that prompt.

Unfortunately, if you do enter something into that field it will be written into all issues that a moved during that session, overwriting whatever was already there.

You will need to change your filter to select all the issues you want to move that also do not have a blank Description field, and move those first. Then you should not be prompted to fill in the Description field during the move.

Then you can do a second bulk move for the issues that do have blank Descriptions, and fill in the prompt once for text to be added to all the issues you are moving at that time.

Kseniia Trushnikova

Hello @Abby O_Connell,

This error means that Description is set to be required in the destination project field configuration and some of your stories don't have Description. If you click Retain and type some text into the form, this text will be added only to stories without Description. No data will be lost for those stories which already have Description filled.

You can also just temporally set Description optional in the destination project field configuration and move stories safely without adding any default Description.

Kseniia Trushnikova

Hey Trudy,

if you do enter something into that field it will be written into all issues that a moved during that session, overwriting whatever was already there.

Even with Retain selected?

Trudy P Claspill

I have not actually tested that.

You could test it by moving just two issues; one with and one without a Description.

Kseniia Trushnikova

I've run a test and it worked correctly with the selected option Retain. No data was overwritten in issues.

I just thought for a moment from your answer that I might have some custom configurations in my Jira that made this test successful

Didier Ernotte_7yb3o1

I have the same problem, the Description field does not follow the migration. I was wondering if the problem came from the type of source project because my source was a team managed project and destination was a company managed project, so I tested the migration from a company managed to another company managed and it worked fine.

So it seems like there is a problem with the migration from a team managed to a corporate managed project.

Trudy P Claspill

@Didier Ernotte

The original poster flagged their post as being for Jira Server/DC, not Cloud, so your situation and their situation are different.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

bulk-edit