Implications of replacing Assignee Field with a "Responsible" Custom Field

Doods Perea4

We have a requirement of assigning JIRA tickets to more than one users, and decided this can be done by creating a custom field of multi-user picker type that will accept one or more values. The Assignee field will therefore be disabled from the project.

The challenge/question(s) are: what would be the implication of disabling (hiding) the Assignee field? I understand the Screens, Notification, Permission and Workflow configurations (and probably mail content wording) will have to be updated. Are there other configuration in the project that I am missing here?

Thanks in advance for your help.

EddieW_h8oivr

Some other things to consider.)

* Assignee is one of the only fields that can be locked for editing to spefic roles/users("Assign Users" permission)

* Many built in filters will break (i.e. "My unresolved issues")

* The quick search "my" keyword will break (i.e. "my PROJECT bugs")

== Edit, adding more..

As Doods pointing out the "Assign" and "Assign to Me" would break, likewise the corresponding keyboard shortcuts "a" and "i".

== end edit

And lastly, although I fully understand the need to add multiple people as contributors via a dedicated field, but leaving things responsble to many people may result in a lack of ownership.