broken Hold Statuses Issue

[Jeremy]

This morning we are getting reports of needing to enter reasons for changing sub-statuses where yesterday there was no reason information needed.

Something has happened since the last update last night...can this ne looked into please?

[AlexTumber]

@Jeremy from the release notes for the latest Service Manager update:

• On Hold Request reason not always mandatory when status set to mandatory {PM00176494}

 

Can I ask if your sub status is configured as mandatory or not?

Alex

[Jeremy]

@AlexTumber I have checked it seems that it was mandatory, we didn't believe that is was...I have now updated our sub statuses

[Andrew Spice]

It would seem today ours have switched to Mandatory bar two "Assigned Service/Incident" and changing "Reason required" wont allow me to save the change (while published?). I'm reluctant to switch to Draft while it's actively in use. 

[Jeremy]

@AlexTumber on further investigation any statuses that we added to services appear to all be mandatory now, where previously they were not mandatory.

[Jeremy]

Also I went through yesterday and changed our global statuses to be non-mandatory and this morning they are mandatory again!

[Jeremy]

Can someone help with this, I have included a video of the issue

[Steve Giller]

It isn't saving (if it was, the popup would close on clicking Save) because the Alternative Customer Label is a mandatory field and is empty.

[Jeremy]

Why do you have to enter a Alternative Name...surely that should be optional?

We don't expose this information to the customer so it's a little redundant for us. I have updated this will a full stop which has enabled us to save the status, thanks for the clarification.