Standard Change created as Normal Change

[lars7]

Hi,

On a customer's instance I have 5 standard change templates that are being created as normal changes.

They used to work, but not anymore. I dont know why - but I think it could be related to an instance version upgrade, which was implemented recently. If I recreate the standard change template the issue do not persist. But I am curious as to why this happens. Has anyone else experienced this before and could explain why it happens? 

[Veerabhadra M]

Hi All,

Do we have a solution for this issue? I am experiencing the same behavior. When templates are moved from the DEV instance to UAT and used to raise a standard change, they are being categorized as normal changes instead.

[mike_m35]

Also facing this issue, previously our standard change template was working as intended, but as of the last few days it has been broken without any major changes coming from our end. Now instead of creating standard changes it's trying to create Emergencies which throws a bunch of errors into the frontend while somehow still creating the standard change on the backend. It's very confusing to our users. 

This is the error we are seeing when trying to submit or save, doesn't matter which option we choose these errors appear, but the ticket is still created as a standard on the backend.... but our users don't think the ticket has been created because of the errors so they are submitting it over and over again...

[Dr Atul G- LNG]

Hi @mike_m35 

The error coming as you are trying to change the model when change is not in new state. 

[mike_m35]

I understand that but I wasn't trying to change the model at that point in time, I was merely trying to submit a CHG through the standard change template, which is what the issue is I'm trying to fix. There seems to be something on the backend that tries to switch it to an emergency change after it's been created which is causing all of these issues. 

[Dr Atul G- LNG]

Hi @mike_m35 

What i think here:

U already raised a change with model and type is emergency and now you want to convert this to standard change by applying standard change template which will not work.