is there an easy way to prevent the default change form from overriding status in a change template

Rod_Marten

We have several steps in our change process that occur before a change request becomes "In Progress".  We implemented this in the console with change templates that set a custom status that prevents the "New" workflow from executing.  When our steps are done we change to "In Progress" and the default workflow takes over.

The Cireson Console seems to override the template and force status "New".

First, this is probably a feature request that if a customer creates a template, that that template should probably take precedence over defaults in the application.

Second, is there an easy way to override this behavior?

Thanks
Rod

Tony_Collett

The Cireson Portal doesn't do any automatic changes to change request statuses.
If you are using a template, does the template have a status which is overriding the existing content? What does the history of the work item say?

Tony_Collett

The Cireson Portal doesn't do any automatic changes to change request statuses.
If you are using a template, does the template have a status which is overriding the existing content? What does the history of the work item say?