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

Project listing is not alphabetically ordered while editing filters

XMLWordPrintable

      Issue Summary

      The list of projects while editing/sharing filters is not strictly ordered alphabetically, there appear to be separate groups of projects in alphabetical order.

      Environment

      • 8.16.1

      Steps to Reproduce

      1. Many projects already existing
      2. Try to share a filter to projects and click on the dropdown list

      Expected Results

      The list of projects should be Alphabetical order.

      Actual Results

      The listing appears to be alphabetical but then other groups of projects are again starting from A. In the screenshot below, the project 'Symphony-TBC' is apparently missing:

      However it is listed further below in another set of projects, as can be seen from the HAR:

      ...
<option roles="[10002,10300,10001,11001,10201,11002,11000,10701,10902,10903,10000,10202,10600]" value="12016">Symphony</option>
    
<option roles="[10002,10300,10001,11001,10201,11002,11000,10701,10902,10903,10000,10202,10600]" value="25208">Symphony-TBC</option>
    
<option roles="[10002,10300,10001,11001,10201,11002,11000,10701,10902,10903,10000,10202,10600]" value="11900">System IS Danderyd</option>
    
<option roles="[10002,10300,10001,11001,10201,11002,11000,10701,10902,10903,10000,10202,10600]" value="22700">TABS DevOps</option>
...

      Notes

      This could be considered an improvement as well but since the behaviour is not consistent across the product we consider this a bug

      Workaround

      Currently, there is no known workaround for this behaviour. A workaround will be added here when available

        1. Screenshot 2021-10-27 at 7.43.40 PM.png
          Screenshot 2021-10-27 at 7.43.40 PM.png
          215 kB

            [JRASERVER-72976] Project listing is not alphabetically ordered while editing filters

            Michał Pastewski (Inactive) added a comment -

            Hi Everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collected 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,
            Jira DC Team

            Michał Pastewski (Inactive) added a comment - Hi Everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collected 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, Jira DC Team

            Ralf Fehling added a comment -

            +1

            Ralf Fehling added a comment - +1

              Unassigned Unassigned
              emarghidan Eduard M
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: