Allow fields to be hidden/edited when certain group or users views a ticket i.e field-level security

XMLWordPrintable

    • 3,209
    • 387

      Atlassian Update - 3 December 2024

      Hi everyone,

      Thank you for sharing your suggestion and participating in the voting process. Your feedback plays a crucial role in shaping and improving Jira for our entire user community. Due to the large number of feature requests we receive, we need to focus on those that deliver the greatest value to the majority of users. After careful consideration, the team has determined that we cannot implement this suggestion in the near future.

      However, we will keep this feature request open and encourage you to continue sharing your use cases and providing additional context. This input will help us better prioritise it for potential consideration in the long term.

      Thank you for your understanding and support!

      Ahmud
      Product Manager-Issue View 

       

      Summary

      Currently it is possible to restrict access to projects and tickets. It is not possible to restrict field visibility/editability however. It will be nice to have a function that can prevent certain users/groups to view/edit specific fields as they may be confidential.
      The ticket is accessible but some fields might contain some confidential information that best left hidden.

      Workaround

      This workaround consists of configuring your project so the desired field(s) will not be editable via issue view, but only via a restricted workflow transition accessible only by people that should be able to edit the fields in question. See the recording where I show an example: Restrict field's editing.mp4

      Alternate Workarounds & Add-on Suggestions

      1. Use “Field Contexts” + Screen Schemes (for view restriction workaround): While Jira doesn’t natively allow field-level visibility control, you can simulate it by:
      • Creating separate screens (e.g., one with the confidential field and one without).
      • Associating these screens to different issue operations or workflows.
      • Limiting access via workflow conditions so only specific roles (like Admins or Managers) transition to screens that expose the confidential fields.

      This won’t hide data from API or search, but it limits casual visibility through the issue view UI.

        1. Restrict field's editing.mp4
          22.02 MB

            Assignee:
            Unassigned
            Reporter:
            Vincent Chin (Inactive)
            Votes:
            518 Vote for this issue
            Watchers:
            364 Start watching this issue

              Created:
              Updated: