• 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.

      1. Most of our projects use components and versions with the same names.

      For example, project A will have components Web, DB, UI.

      Project B will also have components Web, DB, UI.

      Every time we create a new project, the same components need to be recreated. It will be great if we can have a scheme that will automatically provide a list of components.

      2. One screen to edit all schemes for project

      This will be great as currently, every project created, we need to go to Issue Types and change the scheme. Then workflow, change the scheme, then field configuration, change the scheme.
      A single screen to update all these schemes will be great.

            [JRASERVER-30033] Components and version schemes

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3057020 ] New: JAC Suggestion Workflow 3 [ 3685793 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2617625 ] New: JAC Suggestion Workflow [ 3057020 ]
            Thư Nguyễn made changes -
            Link New: This issue is duplicated by JRASERVER-67231 [ JRASERVER-67231 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2586593 ] New: Confluence Workflow - Public Facing v4 [ 2617625 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2362145 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2586593 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2129796 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2362145 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093121 ] New: JIRA Bug Workflow w Kanban v6 [ 2129796 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 884957 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093121 ]
            jonah (Inactive) made changes -
            Description Original: 1. Most of our projects use components and versions with the same names.

            For example, project A will have components Web, DB, UI.

            Project B will also have components Web, DB, UI.

            Every time we create a new project, the same components need to be recreated. It will be great if we can have a scheme that will automatically provide a list of components.

            2. One screen to edit all schemes for project

            This will be great as currently, every project created, we need to go to Issue Types and change the scheme. Then workflow, change the scheme, then field configuration, change the scheme.
            A single screen to update all these schemes will be great.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-30033].
              {panel}

            1. Most of our projects use components and versions with the same names.

            For example, project A will have components Web, DB, UI.

            Project B will also have components Web, DB, UI.

            Every time we create a new project, the same components need to be recreated. It will be great if we can have a scheme that will automatically provide a list of components.

            2. One screen to edit all schemes for project

            This will be great as currently, every project created, we need to go to Issue Types and change the scheme. Then workflow, change the scheme, then field configuration, change the scheme.
            A single screen to update all these schemes will be great.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-30033 [ JRACLOUD-30033 ]

              Unassigned Unassigned
              d55ab01bcca8 Bhushan Nagaraj
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: