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

Loosing comments when moving JIRA User Stories to another project

Harry Bos

We have an huge JIRA project and we have decided we will move a collection of EPIC's with their User Stories to an other project.
There for we per EPIC copy all User Stories first and then we move the copied Uer Stories (to be recognized as CLONE) to the new project.

We found out after comparing old with new that comments do not move along with the User Story ?
Is that a know thin or did we forget something? Are there solutions available / or known so that we can move an issue with comments to our new project?

Accepted answers

Florian Bonniec

I you clone the issue instead of moving them it's normal that the comment has not been copied over. Only custom fields are copied in a cloned issue. Attachments are not copied except if you check the box when cloning the issue but not the comments.

Status is not the same as the original issue as well and will have the value of the first status of the target workflow.

Regards

All comments

Florian Bonniec

Status is not the same as the original issue as well and will have the value of the first status of the target workflow.

Regards

Ste Wright

Hi @Harry Bos

Cloning an Issue created a new Issue based on the field values of the original - this isn't the same as "Move" where you're moving the originals into a new Project.

You have two options...

Move Issue: Move the Issues (using Bulk Change) to the new Project. This doesn't leave a "copied" version behind in the old Project, but is there a need to do that if you're splitting these Issues out?
- See how to Move Issues on this help page
- See how to Bulk Change (i.e Move) Issues on this help page
Export/Import: If you must leave the original version behind and created a copied version of the Issues, you could export the original Issues' data to CSV (including all Fields), then re-import it to the new Project. Using the Admin import options, you can import comments, previous date information, etc.
- See more on this help page

Let us know if this helps!

Ste

Harry Bos

The idea behind first CLONE and then move was/is that if something goes wrong with moving, we still have the CLONE.

Except it turns out the CLONE is not an exact copy of the original. Some data (e.g. comments) get lost.

In the meantime I did a test: created a Dummy-Test EPIC with two dummy-test User Stories. One story with 4 attachments (xls, doc, png, txt) en three comments. The other User Story without anything. Then I moved the 2 user stories in a bulk, Then I moved the EPIC. After renaming the EPIC all was good.

CLONE 'ing will result in loosing comments.
So the plan is I make a backup by exporting tot csv.. just in case we discover that some EPIC or User Story lost info/data during the move. The we move all EPIC related User Stories and then we move the EPIC. We will do it EPIC by EPIC.

Vish Reddy {Revyz}

Hi @Harry Bos

We have a Jira data backup & restore app, using which you can restore back issues and associated comments, attachments etc..

We are in the process of building a workflow which would allow you to restore back copies of data as you call out as CLONE i.e. you can take a "dated" copy of an entire project from the backup and replicate it as a new project, this would include project configuration, issues and its hierarchy of epics and stories and all other objects such as comments, attachments etc..

If you are open to providing feedback on this workflow we are building I would love to further engage with you and share more details.

Ste Wright

Hi @Harry Bos

Move should be fine.

Move effectively is changing the Project and the Key - the rest of the data should remain as-is if the configuration is the same

If not there might be some other changes - eg. different Statuses (which you'd map to), etc.

Ste

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