Change 'tasks' are getting "Closed incomplete", where this is set?

yogesh15dd
Tera Guru

Hi ,

When i click on "Review" (UI action) button on the emergency change, it automatically closes related tasks   state's as well   to "Closed Incomplete",

i have checked it in many of the change_request and task business rules as well as in emergency workflow, no where i'm able to   find this.

find_real_file.png

any idea?

Thanks

Yogish

5 REPLIES 5

Hello!




I agree with Robbie. OOB WFs of the Change Requests (Normal, Standard, Emergency) are the root cause here.



Recently I encountered the same situation.
I was operating on the Change Task level, to say so.


I had to create some custom Change Tasks states and ensure that once the stage of the Change Request goes from "Implement" to "Review" the custom states will stay. Yet, as soon as the transition from "Implement" to "Review" was happening -> the states of the two Change Tasks: Implement and Post Implementation testing were automatically set to "Closed Incomplete". After investigating the matter, I found out that the default "Change Request - Normal" Workflow is responsible for this. [The same is equal also to the Standard & Emergency Change Requests (their OOB WFs have the same logic).]
So, in order to deal with the situation I had to modify the "Change Request - Normal" Workflow by making the following changes:aaa.png


In other words, I set the WF activity Wait for condition (Change moves to Implement) to go directly to the WF activity Workflow (Change request - Normal change tasks) and in the same time, I moved the activities Branch & Wait for condition (Change moves to Review) out of the picture.



Now, once a Normal Change Request of mine goes from "Implement" stage to "Review" -> the "Closed Incomplete" states of the Implement & Post Implementation testing Change Tasks do not appear.




Best Regards,
Georgi Mavrodiev



IT Consultant
Do IT Wise



You may visit us in our Web Site: www.doitwise.com