search cancel

ITL-0002: 'Target Resolution Date' should be same or earlier than 'Impact Date'.

book

Article ID: 252580

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

Given that a RISK is a thing that could happen in the future, while an ISSUE is considered to be happening right now (and RISKS turn into ISSUES if their mitigation strategy fails.

A RISK has an Impact date and a Target Resolution date, you want the resolution date to be BEFORE the Impact date, as you want it to be fixed before it becomes a problem.

Given that an ISSUE has an Impact date and a Target Resolution date, you expect that the Impact date is probably today or earlier, while the Target Resolution is probably somewhere in the future.

When you put a Target Resolution date AFTER the Impact date on an Issue, you received the ITL-0002 error: ITL-0002: 'Target Resolution Date' should be same or earlier than 'Impact Date'.

 

That error makes totally sense for a RISK, but not for an Issue.

Environment

Release : 16.0.3

Resolution

This is working as designed.  Other customers have requested it to work the way it does now.

There is an open enhancement request to make this configurable.


https://clarity.brightidea.com/D919

Title: Business Rule for Date fields in Issue

Description: Give the ability for System Admin to enable/disable business rule, in particular 'Target Resolution Date' should be same or earlier than 'Impact Date' in Issue, it will better support different organizational use cases.