Agile Development > Epic State auto populating to complete on Submit

[BiancaK]

Hi ServiceNow Community

Has anyone perhaps encountered something similar?

In the Agile Development Application I have created a Product, Theme and Epics. When creating an Epic - on load of the Epic form the State = Draft. Once I click on Save / Submit the State is automatically updated to Complete

I have checked if there are any BR, Client Scripts running on the rm_epic table but there is none that is causing this behavior

Any ideas how I can fix this?

[phil_bool_unifi]

HI Bianca.  I can't replicate the issue you're describing in an 'Out of the Box' instance.  
I was able to create a product, and use the related lists on it to create a Theme and an Epic, and by adding the 'Theme' field to the Epic record, I was able to set the theme before saving, with no issues. 

It's worth remembering that Epic (rm_epic) is extended from planned_task, the core table behind projects and project tasks, so you may need to look here too.  Some functionality responds to date values and the 'percentage complete' field.  Are you using the Percent Complete field on your Epics, and if so, could that be automatically updating based on the lack of any child tasks in the epic, to shut the Epic?

Because this issue doesn't occur in "OOB" instances, I suspect customisations of this type are the best place to look for the answer.

[BiancaK]

Hi @phil_bool_unifi 

Thank you for your response. 

Yes, you are correct - there was a customization - and I am trying to undo this customization but need to find it. 

I figured out that when I set the script include "TaskStateUtil" to false then the Epic record State does not auto update to Complete

But at the same time I can see these errors of the BR's that are affected

Will dig further and see if I can find a solution and  will share

Thanks

[phil_bool_unifi]

I hope you managed to find the issue from there.  It looks, from the error, like there's a condition on a business rule that's triggering updates to the epic record which strikes me as very poor practice.  It may be that the taskStateUtil rule has methods embedded in its 'initialize' method that are causing the update.  Otherwise, if the condition has the 'runMarkClosed' method called in it, you may want to evaluate if that is actually a condition, or something it should be doing if the condition is met.