Tasks with dependencies should be created/opened only after its dependent task is closed

Idea ID 1648779

Tasks with dependencies should be created/opened only after its dependent task is closed

0 Votes

PROBLEM:
In a model where more than one task is defined, Service Manager open all tasks at the same time but with different statuses if dependencies between them exists.

To illustrate more: T1 and T2 are defined on Phase A, T1 is dependent of T2, meaning that T2 cannot be worked/closed before T1 is closed.
However, both tasks are opened at the same time when the change is on Phase A being that T1 is Active/Ready phase/state and T2 is Waiting/planned phase/state and will become active when T1 is closed.

Users expect that T2 is not opened (not be there in wait state) until T1 is closed.

REQUIREMENT:
Tasks to be opened as Active/Ready phase/state when its dependent task is closed and not before using any other status.
Users do not find useful having those tasks in waiting state and causes confusion and they try to work on them which is not possible yet.

CURRENT WORKAROUNDS:
None. Users have to ignore those “wait” tasks shown until they become active.

This is related to QCCR1E147429

Tags (1)
1 Comment
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Declined
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.