Cloning of issue doesn't follow new configuration setup for project, when issue being cloned is old

[Girish Jagdale]

I changed the configuration of project and added new custom fields as a Mandatory. Now when someone attempts to clone issue that existed even before changes were made in project, issue doesn't need to have new fields at all.

This allows to creates issues with critical information missing in it and need a solution to handle this condition.

[Ignacio Pulgar]

The Clone feature tends to lead to this and other kind of inconsistencies, like enabling the possibility of creating an issue with values that do not apply to the actual circumstances of the new issue being created.

It's not a surprise that disabling the Clone option in Jira counts with its own How-To article.

It is also possible to forbid Clone option just in a project, by effectively adding the following property to all statuses in use by any of the workflows mapped to the issue types set on that project, which is not very maintainable or recommendable:

jira.permission.create.clone.denied

Please, also note that adding this property may have a negative impact on calls to the API.

Hope it helps.

[Alexey Matveev]

Hello,

You could update all existed issues with the critical information. Then everything would work as expected.

[Girish Jagdale]

Yes we can but then users that are not aware of the changes in project can still keep working on such issues without filling new fields and it would be missed in the report.

One good thing is any edit (using edit button) gives error if mandatory fields are not filled, before saving any change. But this can possibly be not needed.