Routine Administrative Tasks

Occasionally, after initial setup is complete, you will have routine administrative tasks to perform to keep Issue Manager up to date. The following are the most common tasks:

Adding a new user

For a new user, you will need to perform the following tasks:
  • Create an Inbox, if needed, before setting up the account.
  • Set up a new account, associating the account with an existing group and, if necessary, a default inbox.
  • Add the user's Inboxes to the routing rules if the user needs to receive issues through automatic routing.

Removing a user

When a user leaves your organization, you should perform the following tasks:
  • Immediately deactivate the user's account so that he or she can no longer log in. You cannot delete an account if a user has created or modified issues.
  • Replace any references to the user's Inbox in the routing rules with another Inbox. This step prevents new issues from being sent to this Inbox.
    Note: You should make changes to routing rules only when no other users are logged in to Issue Manager.
  • Clear out the user's Inbox by reassigning the issues to other Inboxes.
  • Delete the user's Inbox.

Shifting work assignments

You will need to update group assignments when users change jobs. For example, say that Sarah, a QA engineer, moves to development. You will also need to modify the routing rules so that users will receive issues that are appropriate for their new responsibilities. For example, Sarah should now receive issues that require attention by development instead of QA.

When users change projects, you need to modify the routing rules to reflect their current responsibilities. You also need to make sure that the default inbox is still appropriate. For example, say that Judy is a writer who used to write manuals for Product A, but now documents Product B. Judy's default inbox, Judy - Doc (Product A), should be changed to Judy - Doc (Product B).

Adding new product information

Sometimes you will need to perform the following tasks:
  • Add new products.
  • Add additional releases, platforms, and components for existing products.
  • Change your routing rules to accommodate new products, components, releases, and platforms.