We have a requirement, where we display few fields - like dropdown, labels etc which we want to be read only on the UI screens. These fields still need to be updated using some logic with the APIs so users can see the data. Is that possible?
HiĀ @Manoj Channa
If I understand correctly, you want to restrict the users from editing the fields of the ticket once it is created but you still want some way to update the data in the ticket.
In that case, you can create a group and restrict all other users from editing the ticket except for the members of this group.
Then, as part of the member of the group, you can use the REST API calls to update the ticket details.
Hope this helps.
Thanks,Vamsi
Thank you Vamsi.
This only works if you want to make the issue completely uneditable by all the users.
You can leave stuff like comment, log work, and transition working for them, but they will not be able to amend any data on the issue.
Any further updates on this? We have a similar use case, where we're syncing tickets from another ticketing system over to Jira just for tracking purposes and we'd like specific fields on the issue created in Jira to be read-only.
It looks like you're new here. Sign in or register to get started.
