Clarity Documentation: How Key Tasks affect Effort Task Creation

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• Clarity PPM On Premise

Issue/Introduction

Description:

The current documentation does not clearly describe how the application behaves with respect as to when an effort task is automatically created on actions by the end-user.

To locate the current documentation, navigate to Clarity Home page > click 'Help' > Project Management ? Project Management Overview ? How to Create and Manage Projects

It is stated that -

"It is recommended that you create the project tasks before assigning staff to them. Unless your CA Clarity PPM administrator changes the default setting, a placeholder effort task is automatically created if you staff your project before creating tasks. When this happens, you can either delete this effort task, or redefine its properties and continue to use it. You can create budgets, financial plans, risks, and issues at any time."

Test the following scenarios:

Scenario One:

1. Admin Tool > Project Management: Settings > Set 'Allow Effort Task Creation' to Yes
   
   
2. Home > Projects > click 'New' button > Create a new project
   
   
3. Create a new task, uncheck the 'Key Task' checkbox
   
   
4. Staff a resource to the above project

Result: as expected, no effort task

Scenario Two:

1. Admin Tool > Project Management: Settings > Set 'Allow Effort Task Creation' to Yes
   
   
2. Home > Projects > click 'New' button > Create a new project
   
   
3. Create a task, leave the 'Key Task' box checked
   
   
4. Staff a resource to the above project

Result: an effort task is created. Because the User Guide makes no mention of the different results with the manually created task being a key task or not, users are misled to expect that an effort task would not be created in this scenario either.

Environment

Release: ESPCLA99000-12.1-Clarity-Extended Support Plus
Component:

Resolution

This has been reported as a documentation defect CLRT-64762 and is currently under review for correction in a future version.