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

when we bulk move issues from one project to another Is there any data loss?

Sravani Battu

Hi All,

when we bulk move issues from one project to another project Is there any data loss in issues like attachments, links , comments etc.

Thanks,

Sravani

Accepted answers

Craig Nodwell_7eve9b

Hi @Sravani Battu no nothing is lost. When you do the move the only thing you may have to tweak is any filters that may be using the old issue id.

Nic Brough -Adaptavist-

There can be data loss, it depends on the configuration.

Your system fields and functions are mostly safe, custom fields possibly not. Summary, description, history, comments, attachments - all fine.

The four places you will or may lose data are:

Issue type: If the list of issue types available to a project differ, you may have to change the issue type of issues being moved.
Versions. Versions are project objects. If you move an issue to another project, you lose the versions on it, it can't use versions from outside its containing project.
Components. As versions
Custom fields: Custom fields have a "context" which is either "these issue types", "these projects" or "global". If the context for a custom field does not apply to the target project/issue type, then Jira has to drop any data in it in the source project, because there's nowhere for it to go in the target.

For all of these cases, the loss of the data will be recorded in the history, but dropped from the issue.

All comments

Craig Nodwell_7eve9b

Hi @Sravani Battu no nothing is lost. When you do the move the only thing you may have to tweak is any filters that may be using the old issue id.

Nic Brough -Adaptavist-

There can be data loss, it depends on the configuration.

Your system fields and functions are mostly safe, custom fields possibly not. Summary, description, history, comments, attachments - all fine.

The four places you will or may lose data are:

Issue type: If the list of issue types available to a project differ, you may have to change the issue type of issues being moved.
Versions. Versions are project objects. If you move an issue to another project, you lose the versions on it, it can't use versions from outside its containing project.
Components. As versions
Custom fields: Custom fields have a "context" which is either "these issue types", "these projects" or "global". If the context for a custom field does not apply to the target project/issue type, then Jira has to drop any data in it in the source project, because there's nowhere for it to go in the target.

For all of these cases, the loss of the data will be recorded in the history, but dropped from the issue.

Sravani Battu

Thank you for your detailed info

Sravani Battu

Thank you Craig.

Pazhani Arivarasu

Comments from the existing story will get retained after moving?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server