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

JIRA Admin Helper: Newly added custom events do not show up in the Notification Helper dropdown

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Currently the list is being populated via a WebResourceTransformer. Since the JS resources are cached, changes to the set of Notification Events will not be seen until the cache is invalidated. The ideal solution is to use an ajax request.

      Workaround

      Clicking on the Refresh Client Resources link available in the Look and Feel settings of the Administration section should suffice to invalidate the cached resources from the WebResourceManager

            [JRACLOUD-34000] JIRA Admin Helper: Newly added custom events do not show up in the Notification Helper dropdown

            Dylan added a comment -

            Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage.

            Cheers,

            Dylan - Service Enablement @ Atlassian

            Dylan added a comment - Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage. Cheers, Dylan - Service Enablement @ Atlassian

            Not a problem admin51, glad to help

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Not a problem admin51 , glad to help Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            OK, that worked! Learn something new everyday.

            Thanx!
            -Johnny

            TSO Logic Admin added a comment - OK, that worked! Learn something new everyday. Thanx! -Johnny

            Hi admin51,

            Clicking on the Refresh Client Resources available in the Look and Feel settings of the Administration section should suffice to invalidate the cached resources from the WebResourceManager

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi admin51 , Clicking on the Refresh Client Resources available in the Look and Feel settings of the Administration section should suffice to invalidate the cached resources from the WebResourceManager Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Any simple workaround to force the cache to be invalidated?

            -Johnny

            TSO Logic Admin added a comment - Any simple workaround to force the cache to be invalidated? -Johnny

              Unassigned Unassigned
              edalgliesh Eric Dalgliesh
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: