Jump to content

Recommended Posts

Posted

I have had a few calls recently that seem to be missing comments from the timeline. Is there a system failicty to hide things in the timeline that analysts maybe using I'm not aware off?

 In the example I'm seeing a call has been assigned to someone, then the next item is call taken off hold, but I'm missing the bit that shows call placed on hold. It worries me as we have calls that are against a customer SLA.

 

 

image.png.fa90a96d32a0deae8166469ea4ef0cc5.png

Posted

@chriscorcoran the owner of the request has the option to set the visibility to 'Owner'.  As a result they would then be the only one that could see that particular timeline update.  Also if no visibility default is set against the service sub status it may default to Owner.  Check if the Timeline Visibility option is blank.

 

tlinevis.jpg

Posted

@chriscorcoran the following defect was confirmed today which will directly impact this.  Although I do not yet have a release date for the fix:

Sub-status pop-up

  • When the logged-on person is a Request's owner, "Owner" is selected by default in the visibility selector.
  • When the logged-on person is not the Request's owner but is a member of the assigned team, "Team" is selected by default in the visibility selector.

In conclusion, the default item in the visibility selector is based on your visibility to the Request (returned by Requests::getVisibilityLevel) and the setting "guest.ui.app.com.hornbill.servicemanager.operation.defaultVisibility.hold" is not respected.

The expected behavior is:
If the sub-status has a visibility level defined (in Service > Config > Request Sub-statuses > Edit sub-status > Timeline Visibility field), use that. Else, use the visibility defined in guest.ui.app.com.hornbill.servicemanager.operation.defaultVisibility.hold.

Posted
On 7/14/2020 at 11:25 AM, Frank Reay said:

Maybe showing you the obvious but is this something to do with the Timeline Filter (although the default is All)?

image.png.62fe52f62fb2da3eee70e8f28e93826d.png

Thanks @Frank Reay I checked and thats set to All but I had not used filter before so good shout.

  • 3 months later...
Posted

The fix for the defect identified above was delivered in Service Manager build 2017 released on 9th September 2020: 

  • Corrections to the visibility selector when updating Request's sub-status {PM00163555}

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...