Displays the portlet title "Projects" the following icons:

This control enables you to filter the list of projects displayed in the portlet. The default option is All Projects. When selected, the portlet lists all projects and project groups in the repository. The other options filter the list for a subset of all projects:

When selected displays a table of all projects defined in the repository in the working area. From there you can browse into the projects' structure.

Displays the directories in the repository, either flat or hierarchically depending on toggle in the portlet title bar. Selecting a directory displays contents in the Browser portlet in the working area, and from there you can browse into the structure of any project directory.

Selecting this topic displays a table of all projects in the repository. The table appears in the upper half of the working area.

Available functionality:

Scope: Repository or Project

This topic provides access to user accounts and related management and administrative operations.

Available functionality:

See also: Administrators Guide: User Management.

Scope: Repository only

This topic enables you to view, define, and manage the Roles that can be assigned to users.

Available functionality:

See also: Administrator's Guide: User Management: Configuring User Roles.

Scope: Project only

This topic enables you to view, define, and manage the Roles that can be assigned to users who have access to a project currently selected in the Projects portlet.

Available functionality:

See also: Administrator's Guide: User Management: Configuring User Roles.

Scope: Repository or Project

This topic provides access to the security configuration which defines access rights.

For information about this configuration, see Administrator's Guide: Configuring User Permissions.

Available functionality:

Scope: Repository only

This topic provides access to the global configuration which defines whether or not new users are auto-created from LDAP data.

For information about this configuration, see Administrator's Guide: Configuring LDAP Auto-create.

Available functionality:

Scope: Repository only

This topic provides access to the global configuration which defines data mapping from an LDAP server to Polarion user accounts.

For information about this configuration, see Administrator's Guide: Configuring Polarion to Work with LDAP

Available functionality:

Scope: Repository or Project

This topic provides access to the global or project-specific Overview portlet configuration. Select the scope the Projects portlet.

Available functionality:

Scope: Repository or Project

This topic provides access to the global or project-specific Dashboard portlet configuration. Select the scope the Projects portlet.

Available functionality:

Scope: Repository

This topic provides access to the default configuration of the Overview portlet for all projects without a project-specific configuration.

Available functionality:

Scope: Repository

This topic provides access to the default configuration of the Dashboard portlet for all projects without a project-specific configuration.

Available functionality:

Scope: Repository or Project

This topic provides access to the global or project-specific Shortcuts portlet configuration. Select the scope the Projects portlet.

Available functionality:

Scope: Project only]

This topic provides a GUI for defining and managing Time Points in a project selected in the Projects portlet. For more information about this configuration, see Administrator's Guide: Time Points, and User Guide: Project Planning, Setting Up Work Items for Live Plan, and Time Points.

Available functionality:

Scope: Project only

This topic provides a GUI for defining and managing Categories for a project selected in the Projects portlet.

For more information about this configuration, see Administrator's Guide: Configuring Categories.

Available functionality:

Scope: Repository or Project]

This topic provides access to the global or project-specific configuration files which define custom fields for the different types of Work Items. Select the configuration scope in the Projects portlet.

For more information on this configuration, see Administrator's Guide: Custom Fields. For information on supported field types see Polarion Reference: Administration Reference: Custom Field Types.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration files that define values for various enumerations used in different data fields in the system, particularly for Work Items. For example, you can customize the values for such things as statuses, priorities, and severities. Select the scope of the configuration in the Projects portlet

For more information on this configuration, see Administrator's Guide: Enumerations

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration files that define workflow for all Work Items collectively, and for specific Work Item types. Select the scope of the configuration in the Projects portlet.

For more information on this configuration, see Administrator's Guide: Workflow.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file that controls what data (columns) appear in the Table view for Work Items. Select the scope of the configuration in the Projects portlet.

For more information on this configuration, see Administrator's Guide: Table View.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file that stores saved queries for the scope currently selected in the Projects portlet.

Note that there is a GUI for this configuration: choose Customize Saved Queries in the And field of the Search bar in various Work Item views (Table, Tree, etc.)

For more information on this configuration, see Administrator's Guide: Queries.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file that stores Shortcuts for the scope currently selected in the Projects portlet. Shortcuts are name queries that can be saved in different scopes.

Note that Shortcuts can be created or deleted via the GUI : Use the Query Builder to create the query that provides the desired results, run that query, and save it as a Shortcut. For more information see User Guide: Using Queries and Shortcuts.

For more information on this configuration, see Administrator's Guide: Shortcuts.

Available functionality:

Scope: Repository

This topic provides access to the configuration page that defines the global Working Calendar parameters (i.e. the "normal" work schedule plus any exceptions, for the entire organization). Here you can configure which days and hours are normal working and non-working days/hours, plus exceptions such as holidays. Note that you can configure each user's personal Working Calendar in the User Management : Users topic. Individual users may also edit their own working calendars from their profile page. For more information, see Administrator's Guide: Working Calendar, and User Guide: Configuring your Working Calendar.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file that defines certain defaults related to the planning of Work Items. For example, you can configure the default time estimate value. Select the scope for the configuration in the Projects portlet.

For more information on this configuration, see Administrator's Guide: Planning.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file that controls default values for Work Item linking. Here is where you can set the default value controlling whether or not new Work Items are automatically flagged as suspect. Select the scope for the configuration in the Projects portlet.

For more information on this configuration, see Administrator's Guide: Linking.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file that enables the Voting feature and sets voting limits. Select the scope for the configuration in the Projects portlet.

For more information on this configuration, see Administrator's Guide: Voting.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file that enables automatic assignment of new Work Items and defines how and to whom they are assigned. Select the scope for the configuration in the Projects portlet.

For more information on this configuration, see Administrator's Guide: Auto-assignment.

Available functionality:

Scope: Repository or Project

This topic provides access to the configuration file in which defines the events that trigger notifications ("work item created", "work item updated" for example), and also specifies the classes of users who receive notifications on each event ("current assignee", "all watchers", for example). Select the scope of this configuration in the Projects portlet.

For more information on this configuration, refer to Administrator's Guide: Configuring Notifications.

Available functionality:

Scope: Repository only

This topic provides access to the configuration file in which you can configure global settings for notifications including:

For more information on this configuration, refer to Administrator's Guide: Configuring Notifications and also see comments in the default global configuration file..

Available functionality:

Targets settings in the configuration files are defined between <notification-config> </notification-config> tags.

Notification events are defined in <event_name></event_name> tags. The following events (and appropriate values of the <event_name> tag) are defined:

Notifications are prioritized so that only one notification is sent to each user about a change. For example, adding an attachment and a comment will result in just one attachment notification if email is the target of both. However the one notification will cover all changes.

Once you have specified notification event you can add a notification target for the event using the following tags:

Each user will receive only one notification if s/he falls in multiple categories - that is, both assignee and current user. Please note that not all targets may be used for every event. For example, it makes no sense to use the assignee target for a project-built event.

The linked work items related events (tag <workitem-linked></workitem-linked>) support the roles attribute, which can limit the event configuration to particular roles (comma separated). If the attribute is missing, then all roles are accepted. Only the first matching configuration for the specified role is used.

Here is an example of a linked Work Item roles definition:

<workitem-linked roles="contains,relates_to">

<current-assignee/>

</workitem-linked>

<workitem-linked roles="implements">

<current-author/>

</workitem-linked>

<workitem-linked roles="implements,contains">

<current-author/>

</workitem-linked>
                      

The above fragment will cause the assignee to be notified when his/her Work Item is marked as contained by, or some other Work Item is marked as related to him. When an implements link is added, then the author of implemented Work Item is notified. The third fragment will never be used, because the given roles are already covered by the above entries.

This example will send notification to the Work Item's current assignee when the Work Item is updated:

<?xml version="1.0" encoding="UTF-8"?>

<notification-config>

<workitem-updated>

<current-assignee />

</workitem-updated>

</notification-config>