Setting Up Users and Groups
For this example, you will need some specific group and user names. You can create users of your choice to populate the new groups; however, all of them must have a resolvable email address. If you need more details about creating users and groups, see the StarTeam Help.
Since you probably have only one email address at your disposal, all of these users will need to have your email address. You will be able to identify who has been notified because their full names will appear in the email.
Create the following users and groups in User Manager:
- From the Server Administration tool, open the User Manager dialog box.
-
Create the following groups and users:
Groups Customer Support group
Marketing group
Product Maintenance group
Product Management group
Research and Development group
Users with the following full names Put these users in the groups that match their names.
Customer Support Person 1
Marketing Person 1
Product Maintenance Person 1
Product Management Person 1
Research and Development Person 1
Testing Person 1
Testing Person 2
Additional users with the following full names Do not put these users in any group other than All Users.
Customer Liaison
EM
General Manager
Notification Agent
PM
QA Manager
The example illustrates a workflow to deal with information captured from a feedback form on a company’s web site.
- When feedback comes in, team leaders must be notified that new feedback has entered the system.
-
If the feedback is a suggestion, it is forwarded to the product manager (PM) for review. The PM decides whether to implement the suggestion.
- If yes, the feedback is forwarded to the engineering manager (EM) for assignment.
- If the feedback is to report a defect in the product, it is forwarded to the EM for assignment.
- The EM assigns the feedback to an engineer. If the engineer does not acknowledge the assignment within 24 hours, the feedback must be assigned to a different engineer.
-
When the engineer is finished with the assignment, the EM is notified and the product change is sent to quality assurance (QA) for testing.
- If the change does not pass testing, it is sent back to the engineer.
- If the enhancement passes QA testing, the customer, engineering, and marketing are notified and the change request is closed.