Applying restrictions to an Issue or Custom Field in Jira Cloud

[Deleted user]

Hey Folks

RE:  Applying restrictions to an Issue or Custom Field in Jira Cloud

We currently have a custom field for our bugs used for Customer Issues.  We divide them as either the customer who has the issue OR if it was found Internal (Found on customer instance while testing).

In other words, if Coke reports a bug, we add "Coke" in the field.  If our QA or TAM finds the bug, we just add "Field Reported"

This custom field is free form.

Issue

Our customer support team usually creates these bugs but over the years we've had many other departments (engineers, QA, TAM and etc.) incorrectly touching this custom field and classify bugs as Customer bugs which at times, they should not be doing.  This has caused reporting issues and constantly spending time eyeballing reports and cleaning them up.  We have many reports that depend on the data to be accurate.  

Engineering townhalls, emails, and constant reminder on process have not helped.

I have not found anything tangible via my searches to help mitigate this.

Has anyone here come across this and can share something they have used to apply restrictions within Jira issues?

Thanks

[Nic Brough -Adaptavist-]

This is a case for automation.  Stop relying on the humans to know it and write a simple script or automation to set the field based on the user's group membership (if internal, set internal, if not an internal group, assume customer)