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

Issue type list in "Create new issue" page contains too many issue types

XMLWordPrintable

    • Icon: Support Request Support Request
    • Resolution: Answered
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • 3.12.3
    • None
    • None

      We have defined a few custom issue types. They are assigned to a special issue type scheme. This scheme (and therefore also these issue types) are only used for one single project, by one single developer. However, when you click "Create new issue" in the top menu, the issue type list contains all these issue types for everybody. Also, when you create an issue with such a custom type on a project that doesn't have the issue type, you get no error message. Moreover, these issue types have a custom field configuration scheme, which is also ignored. In other words:

      1. If none of the projects you have access to use a given issue type, the issue type should not be in the list on the "create new issue type" page
      2. If some of the projects do use the issue type, but not all, trying to create an issue of that type in a project that doesn't have the type should raise an error message.

      Thanks!

            [JRASERVER-16688] Issue type list in "Create new issue" page contains too many issue types

            Diego Alonso [Atlassian] added a comment -

            You are right. The ticket is JRA-11222. I will close this issue and make a reference to the other one.

            Diego Alonso [Atlassian] added a comment - You are right. The ticket is JRA-11222 . I will close this issue and make a reference to the other one.

            Neal Applebaum added a comment -

            There is a ticket for that request somewhere...

            Neal Applebaum added a comment - There is a ticket for that request somewhere...

            svdoord added a comment -

            You were right in the sense that it could be solved in configuration. My misunderstanding was in the fact that the global issue type scheme apparently has ALL issue types automatically. So by creating new issue types, I was unconsciously also adding them to the default global issue type scheme. So maybe this should have been a request for the default global issue type scheme not to necessarily have ALL issue types, and that adding new issue types doesn't automatically add them to the default global issue type scheme...

            svdoord added a comment - You were right in the sense that it could be solved in configuration. My misunderstanding was in the fact that the global issue type scheme apparently has ALL issue types automatically. So by creating new issue types, I was unconsciously also adding them to the default global issue type scheme. So maybe this should have been a request for the default global issue type scheme not to necessarily have ALL issue types, and that adding new issue types doesn't automatically add them to the default global issue type scheme...

            ɹǝʞɐq pɐɹq added a comment -

            I suspect you may have a configuration problem. The support team are the best people to try and help you with this. if this is a confirmed bug, then they will have more evidence regarding the problem.

            ɹǝʞɐq pɐɹq added a comment - I suspect you may have a configuration problem. The support team are the best people to try and help you with this. if this is a confirmed bug, then they will have more evidence regarding the problem.

              dalonso Diego Alonso [Atlassian]
              5ebac5b67ee6 svdoord
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: