Access Control and Data Relationships

1、The relationship between project and execution

A project consists of one or more executions.

• The sprints/iterations of the project are specifically managed under the execution, and the execution column is all the sprints/iterations under all projects.

• It's equivalent to saying that the execution shares the pressure of the project modules and manages the sprints/iterations of the project individually.
• Execution team members can quickly access the Executed Tasks list page from the Execute top-level navigation menu.
• The requirements, versions, use cases, bugs, test orders, test reports, team members, and whitelists under execution will be displayed in the project synchronously. The execution can only be associated with products associated with the project.
• Executed requirements are developed directly from associated requirements under products.

2、Access Control Relationships for Projects and Executions

Privileges Management for projects and executions is independent of each other, but access control for projects and executions is related.

• The project can be accessed, but not necessarily all executions under the project.
• It is possible to access the execution under the project, but not necessarily the project to which the execution belongs.
• When the access control of the execution is inherited, the execution can be accessed only if the project to which the execution belongs can be accessed.
• When the access control of the execution is private, only the team members of the execution and the project leaders and stakeholders to which the execution belongs have access.

3、Data Relationships for Projects and Executions

Some data of the project is synchronized by the execution under the project.

• The requirements, versions, use cases, bugs, test orders, test reports, team members, and whitelists under the execution will be displayed in the corresponding project synchronously.
• Execution can only be associated with products associated with the project it belongs to.
• Executed requirements can be linked directly from requirements in associated products.
• When a project removes a requirement, if the requirement has been associated with the execution under the project, the project can remove the requirement only after the removal is performed under the project.
• When a project removes a team member, if the team member is already in the executive team members under the project, it will prompt whether to remove it at the same time.
• In addition to removing requirements and team members, the removal and deletion of other data in the project only removes and deletes the data in the project, and the data in execution is not affected.

Prompt when a project removes a requirement that has been associated to a project executed:

When a project removes a team member, if the team member is already in the executive team members under the project, it will prompt whether to remove it at the same time.

Click Confirm: Also remove the team member from the project/execution team members.

Click Cancel: Only remove the user from the project team.