Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Current »

This article contains the following topics:

Use the Project Center workspace to perform your project management activities. Only administrators and analyst users can use this workspace.

To access this workspace, navigate to WORKSPACES> PROJECT> Project Center.


Project center is only available in the ISM Service Management edition. This feature is not available in the ISM Service Desk edition.

Project Center Home

From the Home tab, you can perform the following tasks:

  • View a summary of all your projects. The projects display as tiles on the Home tab.
  • Click the tiles for the existing projects to view the details of the project. The project details display on their own individual tab.
  • Create new projects. Click the New Project button on the Home tab to create projects.
  • Filter your projects to display them based on the following criteria:                      
    • Project owner
    • Configuration item
    • Status
    • Priority 

Project Tabs

From the Home tab, click a project tile to open the project in its own individual tab.

On the project tab, you can view the details of the selected project and you can modify them. The project tab contains the following sub-tabs:

  • Task Board: Lets you view, create, and modify the tasks for the project. You can categorize tasks into different lanes. You can filter the task lists and search for specific tasks.
  • Team: Lets you add team members and manage their permissions for the project.
  • Properties: Lets you view and update the properties for the project. For example, project description, objectives, dates, owners, cost, related CIs, and related tickets.

How Organization-based Security Affects the Project Center

The Project Center workspace demonstrates the following behavior when organization-based security (OBS) is enabled for the slice:

  • You can relate projects to an organization only if you are a member of that organization.
  • You can relate projects and tasks to only the components that are aligned with your own organization and the child organizations of that organization. Such components include contacts, tickets, and CIs.
  • Organization-based security does not affect the administrators. When working in the Project Center, administrators can view components from all the organizations in the slice.
  • Organization-based security does not prevent project members from accessing the projects. Project members can access the project and work on it even if they are not aligned to the project organization. However, non-administrator users cannot add a member who is not part of their own organization to their project.
    Example: An administrator creates a project and adds it to organization A. Next, the administrator adds users, who do not belong to organization A, as members to the project. In this case, all of the newly added users can access the project even though OBS is enabled.

Note: For more information, see Enable Organization-Based Security.

How Event Notifications Work

The application sends notifications to project team members for the following events:

  • Modifications to project details, lanes, task details, and project membership or task allocation
  • Reminders for approaching due dates
  • Expiration of a due date
  • Violation of budgetary limits

Each notification provides the following details:

  • Type of update
  • Project ID
  • Project owner
  • Priority
  • Size (duration) of the project or task

The application sends the notifications to the user that performed the modifications.

Who Can Use Project Center

Administrators and analyst users can view and use the Project Center workspace. Self-service users cannot view this workspace.

Administrators can view and modify all projects on the slice.

Analysts can view only the projects where they are added as team members. However, for project modifications, analyst users require editing permissions in individual projects. Analysts can encounter the following behavior while interacting with a project:

  • The analyst is not a member of the project: The analyst cannot view the project
  • The analyst is a member of the project: The analyst can view the project and can participate as a team member.
  • The analyst is a member of the project, with Project Admin privileges for that project: The analyst can view the project and can participate as a project administrator.

In the context of project team management, a project can include the following types of members:

  • Project Owner: The project owner always has Project Admin privileges.
  • Project member without Project Admin privileges: The member can only update the tasks within the project.
  • Project member with Project Admin privileges: The member can also update project properties, team, and task lane structure in the project.

The following table describes the project management actions that each type of user can perform.

Action

Project Member (Project Admin)

Project Member (Not a Project Admin)

Administrator (Project Member and Nonmember)

Self-Service User (All)

Analyst (Nonmember)

Notifications for Task and Project

Y

Y

Y

N

N

Update Project Properties

Y

N

Y

N

N

Relate Ticket to Task

Y

Y

Y

N

Y

Relate Ticket or CI to Project

Y

Y

Y

N

Y

Read User Allocation to Project

Y

Y

Y

N

N

Read Task by Visibility When OBS is enabled

Y

Y

Y

N

Y

Read Projects by Visibility When OBS is enabled

Y

Y

Y

N

Y

Read Projects Assigned to me

Y

Y

Y

N

N/A

Read Project

Y

Y

Y

N

Y

Read Lane

Y

Y

Y

N

N

Modify User Allocation to Project

Y

N

Y

N

N

Create Project

N/A

N/A

Y

N

Y

Create and Update Task

Y

Y

Y

N

N

Create and Update Lane

Y

N

Y

N

N

Add Attachment to Task or Project

Y

Y

Y

N

N

  • No labels