Global Visibility

What does Global Visibility mean?

JEMHC configuration is mainly restricted by Admin or Project Admin permissions. In some scenarios, data exposure of specific configuration is required to allow functionality for the Adhoc notification feature.

Open

For example, with AdHoc, it is required to ensure that Jira Users accessing AdHoc from within a Jira Issue can successfully send AdHoc notifications. In order to do this, the ability to select and edit configuration (Such as Template Set content, or Static Resources) is required.

Please read on for further information on what data is accessible by a Jira User from the Adhoc context.

What data is exposed?

Currently, the following configuration is marked as Global:

• Template Sets

• Themes

• Static Resources

• Scriptlets

• Translations

What does this mean for customer use?

When creating configuration that is marked with Global visibility, it is advised that users do not submit sensitive information that is not intended for Jira User access.

For example, when creating a Template Set, it is advised to not include sensitive information in the Template Set content. If you do, a Jira User with AdHoc permission would have the ability to select the Template Set, providing access to the sensitive information stored in the content.