Why is history lost when you move an issue?

[Karie Kelly]

When I move an issue from one project to another, the screen definitions have the same information, but the work flows are different. However, when I move them, the history of any changes/updates that occurred in the first project disappear.

It this the expected behavior or a bug?

Seems like an auditing/tracability issue when all information is lost.

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

You shouldn't lose any history when you move issue from one project to another. If that happens, it is a bug.

[Thomas Schlegel]

Maybe you cloned your issue and then moved it ?

As Jobin said, moving an issue does not remove its history, even if it changes the workflow and the issuetype. You can always see the history in its change history.

[Norman Abramovitz]

I have only seen this issue when workflows are actually different. The workflows have to be shared (ie really the same) not a copy of the workflow.

[Thomas Schlegel]

@Norman: I've tested this with two test projects that have totally different workflows. Even then the history of the issue is not lost.

[Norman Abramovitz]

Interesting, maybe I need to contact support then after I go over what I did before. Thanks for taking the time to test this out.

[Nic Brough -Adaptavist-]

To confirm Thomas' experience, I've been moving issues around all day today, and have a full history on all of them. Definitely one for support - one of the main reasons for using an issue tracker is that you know the history of the issue!

[Karie Kelly]

I really appreciate everyone's feedback. I'll definitely log a support ticket as we are losing all history once an issue is moved to a project that has a different workflow. Thank you!