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

As an Project Administrator, if I type a new Component but remove it, JIRA still notifies me as I if created a component

    XMLWordPrintable

Details

    • 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

    Description

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

      It seems like the green "issue created" notification flag notifies you now if you have created a new component. This is great, a neat feature. However, if you cancel or close that Component before submitting the issue via the Create transition, the Component does not created. This is expected.

      The bug is that the success "issue created" notification flag still notifies you as if you created a Component.

      You must be project admin to add components

      1. Open the Create Issue dialog
      2. Fill in the Summary and add a Component that doesn't exist
      3. Close the new Component
      4. Create the Issue
      5. Look at the notification
      6. Notice that the component hasn't actually be created

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          10 kB
        2. screenshot-2.png
          screenshot-2.png
          7 kB
        3. screenshot-3.png
          screenshot-3.png
          25 kB
        4. screenshot-4.png
          screenshot-4.png
          6 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              38c2db200d62 Steven F Behnke
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: