Hide Issues based on field value

Question

HI - I am looking for a way to hide issues from certain project roles if a field is selected.

Business scenario - I work for a consulting company and we created risks and issues as issue types. We want to be able to track risks and issues in Jira but be able to hide certain risks and issues from our customers (call them internal risks/issues)

Walter Buggenhout · Accepted Answer

Hi @Eric Lynch and welcome to the Community!

You can't do this by a field you select in Jira. However, this looks like a scenario where issue level security may be the appropriate solution.

In short, you define visibility groups in an issue security scheme. Following your description, this might be internal or public - but you can specify levels with any names you think are suitable.

Once properly configured and linked to your project, you should be able to use these levels to set the visibility of each issues individually. Make sure to set the most commonly used level as the default setting for new issues, so you don't hide issues from users by accident.

Configuration instructions are in the linked article.

Hope this helps!

Evgenii · Accepted Answer

Hi, @Eric Lynch

To streamline your workflow in Jira, you can integrate @Walter Buggenhout  suggestion with automation features.

Here's a practical approach: Set up an automation rule that adjusts the issue's security level based on changes in a specific custom field. For instance, when an issue is created or when you modify the 'Risk Type' field after the issue's creation, the automation can kick in. If you select "Internal" as the value, the automation will automatically update the issue's security level to "Not seen to customer." This ensures that sensitive information remains confidential and is not visible to external parties.

Tim Kopperud · Accepted Answer

Hi @Eric Lynch, welcome to the Atlassian Community.

I would recommend using the Issue Security feature for this, as suggested by @Walter Buggenhout. It's right that a field value is not linked to any security setting for an issue.

If the requirements needs a field value to define issue security you can implement this by combining Issue Security and Automation.

After configuring Issue Security on you project you can add an Automation rule that sets the issue security level. Below you see an example.

This example, when an issue is created it checks if the field label equals VIP, and if so the security level will be set to HR Managers.

You will need to apply your own rule settings based on your project (field name, field value, and security schem and level).

I would also suggest that you add a rule when your field value is changed so that you set the correct security level based on the new value.

TimK.