Team inheritance support OR relationships
S
Scott Munro
At present it supports inheritance from a single blueprint.
Where you have multiple blueprints which a PR entity can be associated with e.g.
- Microservice
- Tooling
- Library
Would be nice to add OR tooling OR library where a relation doesn't exist on the initial check to complete the coverage of options for inheritance
A
AnilKumarReddy Gajulapalli
Our desired ownership model is as follows:
- The _user blueprint has Direct ownership (title: Teams).
- Each Jira Issue has a single assignee relation to _user (many: false), which represents direct ownership.
- A Jira Sprint relates to multiple Jira Issues (many: true), with an intended ownership path of jira_issue.assignee.
We want Jira Sprint ownership to be derived by aggregating the assignees of all Jira Issues in the sprint, so that all issue owners are reflected at the sprint level. If this capability to be added, as it more accurately represents real ownership at the sprint level and aligns with our data model.
T
Travis Gosselin
Have this situation as well, where working with multiple inheritance path of permissions would be helpful. In addition being able to configure for multiple inheritance with AND tooling AND Library would be beneficial.