When we copy or clone an issue into a project with a required field, that field is not shown in red and the user is not aware he/she needs to fill it in. The field in question is NOT in the source project so the user needs to fill it in when doing the copy or clone, but often miss that. JIRA simply fails to save silently. Nothing happens unless/until the user fills in the field and re-clicks save. This confuses the users
Is this a known issue and is there a solution?
That shouldn't be the case. Are you sure the field is required for the issue type you are cloning? What version of a JIRA is it? Might be a bug if it is the latest!
PS: Are you using a plugin functionality to clone? Or the default JIRA clone?
We fixed it.. due to an issue in an earlier release, the field was not itself required, but it was required in some issue types. Making it required for the project, then removing from the issue types where it was not needed fixed the problem. We updated to JIRA 7x and apparently the settings were a left over work around from earlier
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs