Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-72022

Add Field Level Security for JIRA Cloud

    XMLWordPrintable

Details

    • 85
    • 54
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Problem Definition

      The customer wants to add field security to certain fields in the project.

      Suggested Solution

      The customer should be able to add field security to certain fields in the project.

      Why is it important

      The customer would like to hide fields from certain users due to confidentiality.

      Workarounds:

      1- There are some apps that are capable of this, such as Secure Custom Fields - Security & Permission - for Jira. However, these are paid after 30 days of activity. You can trial the apps free for 30 days to determine if they suit your needs. 

      2- Another workaround involves adding the Value field to a screen that is displayed when transitioning the issue (transition screen). The transition can be configured to only be performed by the required users (by using a workflow condition). This ensures that only the required users can update the Value field. A brief set of instructions on how to achieve this is provided below;

      1. In your screen scheme, add the Value field to the 'Edit issue' screen only
      2. Create a new screen and only add the Value field to this
      3. In your workflow, add this screen to a transition
      4. Create a condition on this transition so that only some users/groups are able to perform the transition

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              6490eb471916 Craig Wells
              Votes:
              52 Vote for this issue
              Watchers:
              47 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: