Will I lose data after migration from team-manged project to a company-managed project.

[Ansu Achu]

I'm trying to migrate team-manged project to a company-managed project. I've created the company managed project, no additional configuration is done. Now when I do Bulk change all will it get deleted from the team managed project ? Also after migration can I add the custom fields?

[Nic Brough -Adaptavist-]

It's a known annoyance or design failure in the "move" process.  The screen lists all the potentially affected status no matter what, if there's might be a change needed.

You can completely ignore any line that says "0 issues affected".   You will do no damage if you let them all "migrate" to the defaulted value, as no issues will be affected.

Just be very careful to check for all the non-zero results.

[Paul Stephens]

Even when they're all 0 - it's a scary screen!

[Nic Brough -Adaptavist-]

Yes, I totally agree, especially as the 0s are in small, weaker contrasting boxes, so it's easy to miss a non-zero when you're checking a list of 70 or so issue types.

[Rodrigo Sandrini]

Yep, you were right. Clicking "associate" didn't kill my prod system...lol.

I wasn't happy with not knowing and researched, researched, then I finally researched.

Here's the answer: every issue type one is not using on a project will still get assigned by default to a workflow in your project as part of a group containing "all non assigned issue types" and precisely the workflow I was trying to replace hence the reason why i saw that during Publishing.

--------

I tend to question JIRA more because it allows me to create custom field with the same display name of another one, which effectively broke another project some time ago. Obviously, someone was probably calling the display name of a field in code, but it was no excuse of JIRA forallowing me to do this in the system. 

------

Anyway, appreciate the quick responses. Thank you for jumping in to help so quickly.

;)