Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34000

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

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 11 October 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 11 October 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? 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

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

            Pawel Drygas (Inactive) made changes -
            Labels New: incomplete low-interest
            Pawel Drygas (Inactive) made changes -
            Current Status New: {panel:title=Atlassian Update – 11 October 2019|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
            Hi everyone,

            After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as *Timed Out*.

            Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our [Bug Fixing Policy|https://confluence.atlassian.com/support/atlassian-bug-fixing-policy-201294573.html].

            To see what the Jira team is currently working on and has recently delivered see the following dashboards:

            * [Jira Server and Data Center: Recently resolved issues|https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=85597]

            * [Jira Server and Data Center: Current work and future plans|https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=85890]

            * [Jira Server and Data Center: Bug Fix Board|https://jira.atlassian.com/secure/RapidBoard.jspa?rapidView=2418]

            We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

            Thank you,

             

            Pawel Drygas,

            Jira Server Bugmaster
            {panel}
            Pawel Drygas (Inactive) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2843782 ] New: JAC Bug Workflow v3 [ 2929627 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2580961 ] New: JAC Bug Workflow v2 [ 2843782 ]
            Status Original: Verified [ 10005 ] New: Gathering Impact [ 12072 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1537095 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2580961 ]
            jonah (Inactive) made changes -
            Description Original: 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.

            h3. 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}}             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-34000].
              {panel}

            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.

            h3. 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}}
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-34000 [ JRACLOUD-34000 ]
            Confluence Escalation Bot (Inactive) made changes -
            Support reference count New: 1

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

                Created:
                Updated:
                Resolved: