I have a case where I want issues to be classified according to the "customer" who submits them.
I have a field "Customer" with all customers I want, but I don't want each customer to view the list of customers, I want the field to be read-only and set automatically to the customer who is creating the issue.
An alternative solution would be to implement security levels for each customer. That is assuming that you not only want to prevent customers from seeing other customers, but you also want to prevent customers from seeing issues from other customers. This is an out of the box solution.
If you want the solution that you describe, you could use the script runner plugin to set the customer field based on the reporter and then make that field read-only. I have such a script, but it is based on groups in Crowd so it may not fit your situation. In any case, I can provide it if you want it.
Well, yes, that's what I want to do with "Customer" filed; to set issue security.
When the reporter is from our company, he/she selects the customer we want to create issue for, and the security level is automatically chosen according to the customer field.
but I don't know what I should do when the reporter is one of the customers.
If you think your script might help, and it is easy to modify based on our needs, please provide it.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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