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

Assign schemes at the Project category level

XMLWordPrintable

    • 8
    • 7
    • 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 - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      This suggestion is a priority for the JIRA development team, but I am not able to provide an accurate estimate for when this will be resolved. We will update this issue as soon as we can confidently project a release.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      It would make life easier if we could assign the following at the Project Category level and then override at the Project level:

      Notification Scheme:
      Permission Scheme:
      Issue Security Scheme:
      Workflow Scheme:

            [JRASERVER-4505] Assign schemes at the Project category level

            Jeanne Howe added a comment -

            In 2015 "This suggestion is a priority for the JIRA development team"

            8 years later it is still not implemented.

            If the SLA for a "priority" issue is > 8 years, that certainly explains the11,000+ issues in their backlog.

            Jeanne Howe added a comment - In 2015 "This suggestion is a priority for the JIRA development team" 8 years later it is still not implemented. If the SLA for a "priority" issue is > 8 years, that certainly explains the11,000+ issues in their backlog.

            April added a comment -

            Can't begin to say how grateful we would be for this feature....

            We need a solution for those times when there's 500+ projects to update.

            You know what could be ideal and cover the concerns people have mentioned? A checkbox interface, e.g. I can select Category X and then I can check 'select all' but still uncheck any 'special' projects which should not be updated.

            Else, Jason Kemp's idea to make "a new "Project Scheme" setting that encapsulates all the other settings schemes into one setting to change" was also very interesting and possibly more flexible.

            We'll take anything that makes this less painful, especially if there's an API to call it with

            April added a comment - Can't begin to say how grateful we would be for this feature.... We need a solution for those times when there's 500+ projects to update. You know what could be ideal and cover the concerns people have mentioned? A checkbox interface, e.g. I can select Category X and then I can check 'select all' but still uncheck any 'special' projects which should not be updated. Else, Jason Kemp's idea to make "a new "Project Scheme" setting that encapsulates all the other settings schemes into one setting to change" was also very interesting and possibly more flexible. We'll take anything that makes this less painful, especially if there's an API to call it with

            Eduardo Martines added a comment -

            Nice to have, we're missing this feature

            Eduardo Martines added a comment - Nice to have, we're missing this feature

            Tom Lister added a comment -

            I use the categories to drive scrip runner scripts to apply changes. We have large numbers of projects with shared configurations.

            I would like to have multiple categories to assign for different slices of the data. We have project sets that cover global teams but sometimes I only want to update a subset like EU

            I'm going to investigate creating project properties to use as grouping in scripting.

            Tom Lister added a comment - I use the categories to drive scrip runner scripts to apply changes. We have large numbers of projects with shared configurations. I would like to have multiple categories to assign for different slices of the data. We have project sets that cover global teams but sometimes I only want to update a subset like EU I'm going to investigate creating project properties to use as grouping in scripting.

            emilieL29 added a comment -

            It would be very helpfull 

            emilieL29 added a comment - It would be very helpfull 

            Jason Kemp added a comment -

            Having dealt with this for a long time, I've come to the conclusion that the existing Project Category, specifically, shouldn't be used for this feature. We currently use Project Category for roughly division/department groups with multiple projects which aren't always the same as the project settings.

            What there should be is a new "Project Scheme" setting that encapsulates all the other settings schemes into one setting to change.

            Jason Kemp added a comment - Having dealt with this for a long time, I've come to the conclusion that the existing Project Category, specifically, shouldn't be used for this feature. We currently use Project Category for roughly division/department groups with multiple projects which aren't always the same as the project settings. What there should be is a new "Project Scheme" setting that encapsulates all the other settings schemes into one setting to change.

            Oleksandr Chalyi added a comment -

            We are running Jira server instance with over 300 projects and > 1600 users.

            It would be much easier to maintain and administer Jira if we could associate Workflow Schemes/Permission Scheme/Issue Security Scheme with Categories.

            Oleksandr Chalyi added a comment - We are running Jira server instance with over 300 projects and > 1600 users. It would be much easier to maintain and administer Jira if we could associate Workflow Schemes/Permission Scheme/Issue Security Scheme with Categories.

            April added a comment -

            We were just discussing this issue again today. We use project category to indicate (among other things) shared configurations, We will be moving a team to a different project category next month, which means a lot of manual effort to add that project to various field configurations, update project schemes, etc.

            It would be AMAZING if we could just change the category, which would then step us through a project migration process, especially if it could include field configuration, e.g. "Field X is not valid for Category Y. Would you like to add it?" "Oh heck yes!" (click) "Done."

            April added a comment - We were just discussing this issue again today. We use project category to indicate (among other things) shared configurations, We will be moving a team to a different project category next month, which means a lot of manual effort to add that project to various field configurations, update project schemes, etc. It would be AMAZING if we could just change the category, which would then step us through a project migration process, especially if it could include field configuration, e.g. "Field X is not valid for Category Y. Would you like to add it?" "Oh heck yes!" (click) "Done."

            April added a comment -

            Please do this for SERVER, not only DC

            April added a comment - Please do this for SERVER, not only DC

            Jared Pace added a comment -

            PLEASE DO THIS

            Jared Pace added a comment - PLEASE DO THIS

              Unassigned Unassigned
              a8455a07a4ec Robert Castaneda[ServiceRocket]
              Votes:
              202 Vote for this issue
              Watchers:
              86 Start watching this issue

                Created:
                Updated: