Create Custom Field makes TWO custom fields if there is a bad plugin searcher around

XMLWordPrintable

    • 5.01
    • Severity 2 - Major
    • Hide
      Atlassian Update – 06 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      A bit sketchy, but I have reproduced this reliably under the following circumstances:

      1. Have a plugin which defines a Custom Field Searcher, that when initialised in code blows up (unsatisfied dependency in constructor, for example)
      2. Start JIRA with that plugin
      3. Go to add a Custom Field
      4. Choose any type (e.g. Date Time)
      5. Advance to the "details" screen

      When you get here, if you look in JIRA logs, you'll see that something blows up. After this, you can continue to add your custom field instance fine, but when you're done and you're back on the list of Custom Fields, you'll see the new one in the list twice.

      Confirmed this on 5.1.6 and 5.2-SNAPSHOT. Did not happen on 5.0.

            Assignee:
            Unassigned
            Reporter:
            Michael Tokar
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: