Group Properties

Groups have a number of properties. Basic group information (such as a group’s name) are specified in SilkCentral’s Administration module under Administration/Users/Groups (see the SilkCentral Administration Guide for detailed information). Issue Manager-specific group settings like the initial issue states and certain security privileges are specified on the Groups dialog (Issue Manager/Configuration/Groups).

Note A group must be created in SilkCentral before you can modify Issue Manager-specific group settings within Issue Manager.

Required unique name for a group, up to 20 characters.
Example: Documentation.

Note Existing group definitions cannot be edited in Issue Manager. Edit them via the SilkCentral Administration module (Administration/Users/Groups).

Optional description of the group, up to 80 characters. Example: “Documentation produces all technical publications, including manuals and release notes.”

Note Edit the group description via the SilkCentral Administration module (Administration/Users/Groups).

Users must be assigned certain roles. Edit account and role assignement via the SilkCentral Administration module (Administration/Users/Groups). See the SilkCentral Administration Guide for detailed information regarding user roles and account assignment.

A group must be assigned to a project (or multiple projects). Users assigned to a group have access only to the projects that are assigned to the respective group. Edit project assignement via the SilkCentral Administration module (Administration/Users/Groups). See the SilkCentral Administration Guide for detailed information regarding user groups and project assignment.

The initial issue state is the first state assigned to a bug, enhancement, or documentation issue when it is submitted by members of a given group. Different groups can have different initial states for the same type of issue. Moreover, within a group each issue type (bug, enhancement, and documentation issue) can have a different initial state.

For example, you might assign a software bug submitted by members of the Development group to an initial state of Dev-Ready because you assume that developers can accurately assess what is actually a software bug. On the other hand, you might assign a software bug submitted by members of the Corporate group to an initial state of Unreviewed because you might want to first verify that the issue is truly a new bug before sending it on to Development to be fixed.

Issue Manager provides a number of default states for you to choose from. If you want to create your own, do so before setting up your organization’s groups. See “Customizing Workflow”.

Although initial issue states apply to every member of a group, you can explicitly override these settings for a given user (See “Setting Up User Accounts”).

Security privileges define which activities all users in a group can perform. You can assign additional privileges for a given user in a group by editing his or her user account (as described in “Setting Up User Accounts”) but you cannot take away privileges that have been granted to the user’s group.

Security privileges for a group are assigned on the Group Settings dialog. This dialog is accessed via Issue Manager/Configuration/Groups (click the Define Group Settings button or the name of the group you wish to edit). Select a check box to assign that privilege. To give a group superuser privileges, select all check boxes.

Select this check box	To give group members permission to
Groups, inboxes, and user accounts	Create and edit groups, inboxes, and user accounts (including security privileges).
Products	Create and edit products, releases, platforms, and components. Edit the Platforms list and other lists.
Routing rules	Define how an issue moves from one inbox to another based on the product, release, platform, and component it was logged against.
GUI customization	Customize fields and tabs on the Issue Details pages.
Workflow customization	Define issue states and actions, action permissions, help text, and the appearance and usage of action dialogs.
Email notification rules and systemwide triggers	Define email notification rules and add email notification triggers that apply to all issues in the database.
Archive issues	Removes selected issues from the issues and related tables and places them in the ARCHIVE and related tables.

Select this check box	To give group members permission to
Reassign issues	Move an issue from one inbox to another.
Issue verification preferences	Set the Issue verification preference to override the normal routing rules. Preferences are described in the Issue Manager User Guide.
Email notification issue triggers	Add email notification triggers to individual issues.
Enter/edit issues	Permission to enter and edit issues.