Custom Field corrupts project

[Ray Nederpel]

I have a project which is corrupt.

With corrupt I mean eg., sprintreport doenst work (all completed issues are completed outside the sprint), Move to Done doesn't work (both the button as the auto-update when last subtask moves to done JIRA don't work).  

Reason seems to be a custom field because when I create a new project with standard workflow etc all seems to work fine. When I move an issue from my current project to the new project Jira asks what to do with this custom field, a) adjust the new product b) discard this field. When I choose option b) all works fine, when I choose option a) it corrupts my new project.

[Nic Brough -Adaptavist-]

It sounds like there is code around this custom field that you (or one of your admins) has added, which is blocking the transitions, and your your board filter is looking at it.

What is this field?  What does the board filter say, and can you check the "done" transition for conditions, validators and post-functions?

[Ray Nederpel]

Thats what I thougt.

I created a whole new project with default JIRA workflow etc (where everything works fine). Then I moved an issue from my corrupt project to this new project and "voila" it corrupted my new project, without special transitions (with post-functions).

The field is a field for "Team".  Depending on the project there is a different selection list. In the transition create there's a post-function which says to inherrit the value from the issues parent.

[Nic Brough -Adaptavist-]

The use of a simple custom field won't do what you are describing unless you have configured something to make it behave that way based on the field ocntent.

What type of field is "team"?