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

Remove Issue Types from the Default Issue Type Scheme

XMLWordPrintable

    • 8
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Atlassian Update - 27 November 2015

      Hi everyone,

      As of JIRA 7 (released on October 6, 2015), new projects are not created using the default issue type scheme. Depending on which project template you choose, a fresh set of schemes will be created for you. These new schemes do not use the default issue type scheme.

      If you would like to create a project that uses the same schemes as an existing project, we have introduced a new "Created with shared configuration" feature when creating projects. Simply select an existing project, and JIRA will create a new project that shares all the same schemes as the existing project. Learn more here.

      While we have kept the default issue type scheme for now, it is not used by default unless specifically selected and we expect to remove it in a future release.
      Regards,
      Dave Meyer
      Product Manager, JIRA Platform

      By default, all newly created issue types are automatically added to the Default Issue Type Scheme. However, we have some specific issue types for use with non-global projects that need not be shared amongst all other projects. (Most of our projects are using the Default Issue Type Scheme for simplicity.) It would be nice if either:

      1) the "remove" functionality was added to this scheme; or
      2) newly created issue types never even made it to the Default Scheme.

        1. ChangeIssueTypeJRA-11222
          2 kB
        2. JRA-11222.sh
          1.0 kB

            [JRASERVER-11222] Remove Issue Types from the Default Issue Type Scheme

            Dave Meyer added a comment -

            Hi stevenspyrka,

            I'm not aware of the behavior you're referring to and am unable to replicate it. I think it is a separate issue from this one. Could you create a support request or contact me directly?

            Thanks,
            Dave

            Dave Meyer added a comment - Hi stevenspyrka , I'm not aware of the behavior you're referring to and am unable to replicate it. I think it is a separate issue from this one. Could you create a support request or contact me directly? Thanks, Dave

            Jan Solca added a comment - - edited

            Hi Dave

            could you please clarify since it would not make sense to have such a behavior .We planned to migrate to 7 next week.

            bests
            Jan

            Jan Solca added a comment - - edited Hi Dave could you please clarify since it would not make sense to have such a behavior .We planned to migrate to 7 next week. bests Jan

            Steven Spyrka added a comment -

            Hi Dave,

            I am sorry to inform you that you are wrong.
            If I have a project with its own issue type schema with issue type A,B,C,D,E,F and only A and B occur in the Default Schema then I can only move issues to an issue type that exist in the Default Schema. Even if the Default Schema is nowhere assigned.

            Regards
            Steven

            Steven Spyrka added a comment - Hi Dave, I am sorry to inform you that you are wrong. If I have a project with its own issue type schema with issue type A,B,C,D,E,F and only A and B occur in the Default Schema then I can only move issues to an issue type that exist in the Default Schema. Even if the Default Schema is nowhere assigned. Regards Steven

            Dave Meyer added a comment -

            Hi everyone,

            As of JIRA 7 (released on October 6, 2015), new projects are not created using the default issue type scheme. Depending on which project template you choose, a fresh set of schemes will be created for you. These new schemes do not use the default issue type scheme.

            If you would like to create a project that uses the same schemes as an existing project, we have introduced a new "Created with shared configuration" feature when creating projects. Simply select an existing project, and JIRA will create a new project that shares all the same schemes as the existing project. Learn more here.

            While we have kept the default issue type scheme for now, it is not used by default unless specifically selected and we expect to remove it in a future release.

            Regards,
            Dave Meyer
            Product Manager, JIRA Platform

            Dave Meyer added a comment - Hi everyone, As of JIRA 7 (released on October 6, 2015), new projects are not created using the default issue type scheme. Depending on which project template you choose, a fresh set of schemes will be created for you. These new schemes do not use the default issue type scheme. If you would like to create a project that uses the same schemes as an existing project, we have introduced a new "Created with shared configuration" feature when creating projects. Simply select an existing project, and JIRA will create a new project that shares all the same schemes as the existing project. Learn more here . While we have kept the default issue type scheme for now, it is not used by default unless specifically selected and we expect to remove it in a future release. Regards, Dave Meyer Product Manager, JIRA Platform

            Steven Spyrka added a comment -

            + This issue is open since 9 years please fix it now.

            Steven Spyrka added a comment - + This issue is open since 9 years please fix it now.

            Jan Solca added a comment -

            +1 .. semantically "Default" may mean "common to... without specifying particular rule" .... so common to all project .. why should "Custom" Issue Types flow in a default Scheme .. ?

            Please fix this ASAP.
            we also have about 40 projects which should be migrated.. certainly not a panacea ..

            Jan Solca added a comment - +1 .. semantically "Default" may mean "common to... without specifying particular rule" .... so common to all project .. why should "Custom" Issue Types flow in a default Scheme .. ? Please fix this ASAP. we also have about 40 projects which should be migrated.. certainly not a panacea ..

            Fernando Margueirat added a comment -

            Another one bites the dust here. Please change/fix this issue.

            Fernando Margueirat added a comment - Another one bites the dust here. Please change/fix this issue.

            ChrisV added a comment -

            Bitten by this one today, would be nice to see it fixed

            ChrisV added a comment - Bitten by this one today, would be nice to see it fixed

            Young Plugins added a comment -

            Considered this? https://marketplace.atlassian.com/plugins/net.youngaweb.jira.issue-type-ui-filter

            Young Plugins added a comment - Considered this? https://marketplace.atlassian.com/plugins/net.youngaweb.jira.issue-type-ui-filter

            Karlkim Suwanmongkol added a comment -

            +1 This should be very useful.

            Karlkim Suwanmongkol added a comment - +1 This should be very useful.

              Unassigned Unassigned
              1c814bd50353 [ c h r i s d o y l e ]
              Votes:
              249 Vote for this issue
              Watchers:
              131 Start watching this issue

                Created:
                Updated:
                Resolved: