How to only allow certain fields to be editable depending on Status

[Ruska Sisauri]

Hallo,
I found good solution for my Problem :

How to only allow certain fields to be editable depending on Status
https://confluence.atlassian.com/jirakb/how-to-only-allow-certain-fields-to-be-editable-depending-on-status-729482680.html

but...

I still have questions. .
As I notice , If user does not have  permission "Transition issue", he/she can not use this feature , Am i right?   

I really need this solution, but if only I have opportunity to choose the roles and permissions while using this feature.

My process is like this: There is  a role in my JSD Project "Jira sevice desk Viewer" . This role now has one  permission to view issues and I  also want  them to edit (if issue status = Open ) "description" field . "Jira service desk viewer" Role does not have any other permissions , like "Transition Issues and etc/

and there is another question : If you do not have "edit issue" permission , but  have this workaround , you are still  allowed to edit issue, (this workaround is not linked with project permissions)  Is it a bug ? 
Can Someone help me and explain how to manage it?

[Trudy Claspill]

Hello @Ruska Sisauri 

Yes, to use this workaround, the user must have Transition Issue permissions.

Potentially you could add Conditions to each transition to limit who can see the transitions based on their Roles. You would have to give the "Transition Issue" permission to the JIRA Service Desk Viewer role first, and then in all the workflow transitions add Conditions to determine who can see the transition.

However, in order to have access beyond what a Customer has, a person has to be allocated a Service Desk Agent license and has to be assigned to the Service Desk Team role in the project, with that role already having been assigned various permissions in the Permission Scheme for the project. Are you granting the service desk agent license to the people in the "JIRA Service Desk Viewer role? And have you modified the Permission Scheme to give that role access to the project?

Regarding your last question are you saying that you have set up the workaround and found that a person who doesn't have Edit permissions in the permission scheme can still edit the issue in this case?

[Ruska Sisauri]

Thank you Trudy for the response. 
I will try to add some conditions to transitions.
Yes This Role "Service Desk Viewer " has license but.. ( They are just reporters, but because of the customers cant view other users tasks, we have lots of duplicate tasks, so I want to allow them to search tasks by summery, but they can not have transition issue permission .)

And about my last question .. yes i found that if you do not have Edit permission in the permission scheme you can still edit issue ( because of this workaround)

[Trudy Claspill]

Do you use Organizations in your configuration of Service Desk?

If you users are assigned to an Organization, and the Organizations field is set on the ticket, then the users would be able to see all tickets for their Organization through the Customer Portal. Perhaps that would give them the visibility that you want. They would not be able to edit the description, but they could add comments.