Jump to content

On Hold no longer shows as greyed out?


Recommended Posts

Hi @David Hall this is still causing quite a bit of noise for us, as the support teams are struggling with the missing functionality. Seconding the question about whether this can't just be set back to how it was, and when will the 'fix' be implemented?

Link to comment
Share on other sites

@Gavin James - SDDC @StephC @Emily Patrick

Sorry for the delayed reply but I have not been in the office the past week.  

Just to clarify the current situation, the row highlighting is actually still present however with the introduction of the light blue background in the new UI it is no longer clear to see, hence we will alter the colour to be more visible in the next update of Service Manager which will also include a fix for the font formatting which is incorrectly not being applied.  Just to re-iterate the filtering options to the top left of the request list provide for easy filtering of on-hold requests so keen to understand if this is not a viable alternative in the time until we are able to push the next SM update which we anticipate being early next week.

Kind regards,

Dave

  • Like 2
Link to comment
Share on other sites

@David Hall Thanks for the update.  A number of our analysts already have the Status column showing in their views of tickets/queues, but it still doesn't help with quickly being able to identify what tickets are new or open and needing attention. 

Hopefully both issues can be fixed in time for the next SM update next week. 

  • Like 1
Link to comment
Share on other sites

@David Hall appreciate the update!

Unfortunately much like Emily said, analysts have the column showing for status but being able to quickly see by row which tickets are on hold is really being missed. We are getting comments daily from people asking when it will be fixed still, this is a real problem for us and is definitely having an effect on teams.

Link to comment
Share on other sites

From today/yesterday's update it seems that our tickets have a new colour code, the regular dark blue we're used to for dark mode, a new dark red and a very light blue.

This only seems to be an issue in dark mode but as you can imagine it's not very easy on the eye as multiple members of our team has reported this as an issue. 

image.png

  • Like 2
Link to comment
Share on other sites

Good to see the more visible difference between on-hold and active.

 

On-Hold stuff is something that normally needs less attention as such is there a way to configure to make it LESS vivid than the active tickets.

 

I'd be surprised if we were the only ones to want on-hold to be less visible rather than more.

Edit: This is resolved, I had set the font to be bold in the settings, it had just started to show! Setting it to opaque causes it to be sort of greyed out.

  • Like 1
Link to comment
Share on other sites

4 hours ago, Blowerl said:

I see you have darken the on hold calls, but the text is so soft and faint.  Can the text be made sharper.

 

image.thumb.png.a2056534b01a7e58e6808c00d6500241.png

Hi @Blowerl

You are most likely using the default value of 'Opaque' in this service manager application setting webapp.view.ITSM.serviceDesk.requests.list.onHoldFontStyle .  If you change this to 'None' as per attached image it will make the content clearer.

Kind regards,

Dave.

Screenshot 2024-04-23 at 12.00.03.png

Link to comment
Share on other sites

Not sure if this has already been noticed or reported as well, I have a few people who use the dark mode complaining that it is very hard for them to read the on-hold tickets as some of the columns font are white against the light blue background.  Is this also being looked at @David Hall?

image.thumb.png.18c130616cf7d833ba22e2f6c39c3287.png

  • Like 2
Link to comment
Share on other sites

We've had similar issues (dark red highlights) due to previous customisations of the following 2 settings (which worked fine in the old UI):

  • webapp.view.ITSM.serviceDesk.requests.list.unreadColour
  • webapp.view.ITSM.serviceDesk.requests.list.onHoldFontStyle

Reverting these settings to defaults has solved the issues for us.

Link to comment
Share on other sites

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...