Configuring process role relationship rules
Within a lifecycle project, you can configure rules that specify which combination of process roles members should have across the project areas.
Before you begin
About this task
- In the Lifecycle Project Administration user interface, click the Projects page.
- Click the lifecycle project for which you want to configure rules.
- In the Recommended Role Assignments field, click Download to download the configuration rules XML file to a local directory.
- Open the rules file in an XML editor. The file contains <context container> tag entries for each project area in the lifecycle project.
- For each rule that you want to specify, enter a <roleRule> tag.
- Within the <roleRule> tag, enter one <sourceRole>
tag, for one project area, and <targetRole> tags for the other
project area or areas. Use the id attribute to identify the role.
Use the context attribute to identify the project area. The <sourceRole> tag identifies the role assignment that triggers the rule. The <targetRole> tags identify the role assignments that the user should have in the other project areas.
- After you finish entering rules, save the file.
- In the Recommended Role Assignments field, click Update. Click Browse and navigate to the modified XML file.
In the second rule, if a user has the ProductOwner role in the change and configuration management project area, that user must have the contributor role and the Author role in the quality management and requirements management project areas, respectively.
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <configuration xmlns="http://jazz.net/xmlns/foundation/lpa/1.0/"> <context container="https://clmwb.ibm.com:9443/qm/process/project-areas/_HqTYwFA6EeCDEIOn27spMw" id="rqm.project"/> <context container="https://clmwb.ibm.com:9443/jts/process/project-areas/_BfKFIFA6EeC8EOYPIUlkYQ" id="rrc.project"/> <context container="https://clmwb.ibm.com:9443/ccm/process/project-areas/_Cpg_cFA6EeCeyorLOKTSdw" id="rtc.project"/> <roleRule> <sourceRole id="ScrumMaster" context="#rtc.project"/> <targetRole id="tester" context="#rqm.project"/> <targetRole id="Administrator" context="#rrc.project"/> </roleRule> <roleRule> <sourceRole id="Product Owner" context="#rtc.project"/> <targetRole id="contributor" context="#rqm.project"/> <targetRole id="Author" context="#rrc.project"/> </roleRule> </configuration>
If a user does not have the roles specified by the configuration rules, the Lifecycle Project Administration user interface flags the violation on the Members page. For example, in the figure below, Bob does not have the contributor role in the quality management project area.