Hi,
Is it possible to hide a field for Project Role Users and make the same field visible for the Project Role Administrators in JIRA Cloud.
Thanks in Advance!
No. JIRA doesn't have any form of field-level security in it.
There are a couple of tricks you can play if you have Server versions of JIRA, including one add-on that is explicitly for it which works really well, but there's no options for it on Cloud.
Thanks for your response Nic, If there is no option to hide a field is there a possibility to make it read only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Remove the field from the "edit" screen and it will become read-only (leave it on the "view" screen of course).
That blocks all edits though, so you might want to consider having it on transition screen and having transitions that then use conditions to only allow certain users to perform them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm with Nic on putting the field on a protected transition going back to the same status. Depending on the use, you may need to put it on more than one status
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist-, could you please provide me with the solution for the Server? We use Software projects for Customers and want to hide some fields depending on project roles. It is nice to have security permissions for the comments but we would like to have some project-level settings for the fields based on if it is an internal or external user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You will need something like ScriptRunner Behaviours that can show or hide fields dependent on rules.
If you are going to do that, you need to be aware that it is not for security, as the data is still present in the html that goes to the end-user's browser so they can see it, and it won't affect the data or usage of any REST calls.
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.