Post-Installation Tasks → Configuring Users → Adding Members to Groups and Setting Defaults
After creating the groups and setting their roles and privileges, add appropriate users to each group (membership) before continuing to set any default values.
For each of the groups you just created, add at least one user who will fill the role that the group is associated with.
You can set default values so that user name is automatically selected for a group when items are submitted or transitioned. For example, if users will always select “Bob” as the Release Manager, it saves time and effort if “Bob” is already set as the default. Users will be able to change the values in the workflow if necessary.
In situations where a few users are typically selected, creating multiple sub-projects with different default values is an ideal option. For example, there could be a “Release Packages (Team A)” project and a “Release Packages (Team B)” project where “Alice” is the default Release Manager for one, and “Bob” is the default for the other.
If there are more than a few choices, you should not set default values. For example, if a team has dozens of Release Engineers and the users will need to be making a dynamic choice for the correct selection, using default values would not be helpful. Keep this in mind when examining the list of user fields to default. It may make sense to default some, but not others.
This step is optional, and is not required for using the product. If you don't want to do this setup at this time, you can skip to the next section.
To set the default user:
After setting a field to have a default value, the Allow Override option will be selected. This enables you to easily remove the default by deselecting the option.
Project | Transition Name | Field Name |
---|---|---|
Task Template Projects |
Submit |
|
Planning Release Train Projects |
Submit |
|
Deployable Release Train Projects |
Submit |
|
Release Packages Projects |
Submit |
|
Environments Projects |
Submit |
|
Deployment Path Project |
Submit |
|
Approvals Projects |
Planning Exit Criteria Submit Development Exit Criteria Submit QA Exit Criteria Submit [Milestone Submit] |
|
Application Version Projects |
Submit |
|
[Sample Request Projects] | Submit |
|
Copyright © 2012–2019 Micro Focus or one of its affiliates. All rights reserved.