Built-In Project Copy does not work as expected

[Felix]

Hey guys,

I'm trying to copy a project with ~1.300 issues using the built in scripts. At some point I receive a timeout-message without any stacktraces. As i read here the timeout is only a UI thing. After a while all the issues are copied to the new project - so far so good. Now my problem is, that each one of those 1.300 issues has the status "Backlog", which is the first state after creating an issue. In the original project, more than 1.000 issues are marked as "Done". 

So does it have something to do with the timeout? How can I archive that all issues have the same status?

Thank you!

[Maarten Cautreels · Accepted solution]

Hi Felix,

I just gave it a go on my test instance and was able to reproduce this behaviour. All issues came in the first available status.

I'm afraid this is the expected behaviour.

Best,

Maarten

[Felix]

Hm that's quite strange, because for smaller projects it works exactly as expected. And having a different behaviour depending on project size sounds a bit strange to me + there is nothing mentioned in the docs.

I tried it with a project containing ~400 issues, out of those 300 were "Done", 20 "In Progress" and the rest was "Backlog".  The copied project had all the issues in the corresponding status. 

@Maarten Cautreels Can you confirm, that it works with small project? (wanted to post it as an reply but clicked the wrong field)

[Maarten Cautreels]

Hi Felix,

I tried a project with just 67 issues. This was the configuration:

And the result:

Don't worry about the data, it's test data generated by Jumble.

Best,

Maarten

[Felix]

Okay, my fault! I looked into the wrong project :/ 

Any chance that you know a way how I could copy the projects AND maintain the issue status? 

Sorry once again! 

Cheers,

Felix

[Maarten Cautreels]

Hi Felix,

I've found this Knowledge Base article that could help although I haven't test this.

Best,

Maarten