I am hoping there is a solution for my question. We would like to create a field but also restrict access for certain security reasons. While one group of people should be able to create, view or query the field, the rest of the user group should not be able to view data, query or see it as filter results.
Have anybody worked through this issue before?
I only have partial answer for you because I have done this on server systems only:
I have worked with this function before and there are several criteria: the field cannot be a system field and it cannot be a required field because the end user if they do not have permissions to see will never meet the criteria.
check your Cloud documentation for field schema: https://confluence.atlassian.com/adminjiracloud/associating-field-behavior-with-issue-types-776636450.html
and create a field schema for that project.
Hiding it from a filter--that part I have never done.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events