When I move an issue to a particular project a couple of custom fields are displayed on the "Move Issue: Update Fields" screen that are not required on issue creation in that project.
The documentation states that:
You will only be prompted to enter the values for required custom fields in the target project that are missing values. If the custom fields of your original project also exist in your target project, and these custom fields are not required in the target project, you may need to set values for them, to move the issue successfully. If you wish to change the existing values for other fields on your issue, you can do this after the move is complete.
However the unwanted custom fields are not required on issue creation. They are part of the target project's Field Configuration scheme (defined with project contexts not a global context), but I don't want these fields to appear on this initial screen when moving issues.
These are the unwanted fields:
* CSI Subtask type: is only required during a particular workflow transition and only appears on that workflow transition screen (in the target project). Is not displayed on issue creation, view or edit screens in target project.
* Support tier: is set via a post-function in workflow transitions (user is never prompted to enter). Is not required. Is only ever displayed on the Issue View screen (not on Create, Edit or transition screens).
I can hide the fields by removing from the Field Config scheme or setting to "Hidden" in this scheme - but then they can't be used in the project.
Any suggestions or ideas why these fields and not others with similar characteristics are showing up?
Hello, Sandra, for some reason, any custom fields of different contexts from the origin issue will also prompted in the move screen, even if they are not required
For example if you have Project A and Project B, with the following custom fields:
CF1 will not appear in the screen and its values will be ported, CF2 will appear in the screen because it has a specific context in project B, CF3 will also appear in the screen because their contexts are different and CF4 will also appear because it's required.
Hope this helped!
Thx for the explanation. I was wondering why move screen fields seem arbitrary. Here's my background: I have Project A and Project B. When an issue from Project A is assigned to a particular group, it generates a new issuetype in Project B with a deadend workflow. The new issuetype includes a subset of fields from the Project A issue. None of these fields display on the move screen, which is great. Folks from Project B review that new issue and manually move it to a valid issuetype in Project B. This all works great.
I was asked to add another field from Project A issue to Project B issue, so I added the additional field. This field now displays on the move screen (none of the other fields do). After I read your explanation above, I modified the custom field configuration from selecting both projects to Global context. I also re-indexed. The field still displays on the move screen. What did I miss?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events