example: priority can edit only one user like( developer role) but reaming custom fields can edit reaming groups
I am sorry, it is not clear what you are asking for here. I can see it is something to do with editing fields, but the sentences do not make any sense.
Could you explain it again, in a different way?
Still not clear, but I can make a guess. Do you mean:
I want a customer to be able to create an issue, but not edit some of the fields after they created it
Is that right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Customer can create an issue. But only one person can edit particular field values reaming person's can't change that field value. Reaming fields values can change any person
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so you're asking why only some people can edit a field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.