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

Inheritance of project configurations

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 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.

      We'd like to have some tool allowing the following for all project configuration entities - workflows, workflow schemes, screens, screen schemes, issue type screen schemes, etc. Workflows is just an example.

      If we have, for example, three workflows: Workflow A, Workflow A1 and Workflow A2 and workflows A1 and A2 are a little modified versions of the Workflow A. Can we establish some relationship defining that Workflow A1 is a "child" of Workflow A? And when we modify Workflow A, then all its child workflows (A1 and A2 in this example) modifies automatically getting the same changes.

      Can we expect that something allowing to do this will be appeared in JIRA?

            [JRASERVER-33322] Inheritance of project configurations

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3058497 ] New: JAC Suggestion Workflow 3 [ 3686270 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2605062 ] New: JAC Suggestion Workflow [ 3058497 ]
            Thư Nguyễn made changes -
            Link New: This issue duplicates JRASERVER-67231 [ JRASERVER-67231 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2555906 ] New: Confluence Workflow - Public Facing v4 [ 2605062 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339766 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2555906 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2116151 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339766 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2076211 ] New: JIRA Bug Workflow w Kanban v6 [ 2116151 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 879809 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2076211 ]
            jonah (Inactive) made changes -
            Description Original: We'd like to have some tool allowing the following for all project configuration entities - workflows, workflow schemes, screens, screen schemes, issue type screen schemes, etc. Workflows is just an example.

            If we have, for example, three workflows: *Workflow A*, *Workflow A1* and *Workflow A2* and workflows *A1* and *A2* are a little modified versions of the *Workflow A*. Can we establish some relationship defining that Workflow A1 is a "child" of Workflow A? And when we modify Workflow A, then all its child workflows (A1 and A2 in this example) modifies automatically getting the same changes.

            Can we expect that something allowing to do this will be appeared in JIRA?             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-33322].
              {panel}

            We'd like to have some tool allowing the following for all project configuration entities - workflows, workflow schemes, screens, screen schemes, issue type screen schemes, etc. Workflows is just an example.

            If we have, for example, three workflows: *Workflow A*, *Workflow A1* and *Workflow A2* and workflows *A1* and *A2* are a little modified versions of the *Workflow A*. Can we establish some relationship defining that Workflow A1 is a "child" of Workflow A? And when we modify Workflow A, then all its child workflows (A1 and A2 in this example) modifies automatically getting the same changes.

            Can we expect that something allowing to do this will be appeared in JIRA?
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-33322 [ JRACLOUD-33322 ]

              Unassigned Unassigned
              158a9b8b352e Oleg S.
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: