Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-8895

Scheme inheritance: define schemes in terms of other schemes, to factor out commonalities

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      The idea is to allow a scheme (permission, notification etc) to be defined in terms of another scheme, and extend it in some direction. Changes to the underlying scheme would take effect in all 'extending' schemes immediately.

      > More important, however, whould be the possibility to let a project "inherit" the permission scheme of its super project (if there is a super project) and to let a super project inherit the permission scheme of a project group (if there is such a group). So, we're actually looking for permission scheme inheritance in the project group/super project/subproject hierarchy. Of course it should be possible to override the inheritance and specify a custom scheme anyway.

            [JRACLOUD-8895] Scheme inheritance: define schemes in terms of other schemes, to factor out commonalities

            Josh Devenny added a comment -

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Josh Devenny and Roy Krishna
            JIRA Product Management

            Josh Devenny added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Josh Devenny and Roy Krishna JIRA Product Management

            Ben Kearney added a comment -

            I think this would be a neat feature. I think it makes a little more sense than JRA-1566 (both would be cool to have) in terms of subtracting/excluding some item from the parent scheme.

            I am not sure how you would set the precedence of schemes or handle exclusions in the multiple schemes approach; I would simply assume all schemes are additive.

            Ben Kearney added a comment - I think this would be a neat feature. I think it makes a little more sense than JRA-1566 (both would be cool to have) in terms of subtracting/excluding some item from the parent scheme. I am not sure how you would set the precedence of schemes or handle exclusions in the multiple schemes approach; I would simply assume all schemes are additive.

            Jeff Turner added a comment -

            Allowing multiple schemes to be associated with one project (JRA-1566) achieves the same thing as allowing schemes to be defined in terms of other schemes (JRA-8895). I'm not sure which is better.

            Jeff Turner added a comment - Allowing multiple schemes to be associated with one project ( JRA-1566 ) achieves the same thing as allowing schemes to be defined in terms of other schemes ( JRA-8895 ). I'm not sure which is better.

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              5 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: