Nanette

@chriscorcoran Yes, we are currently investigating with the highest of priorities, please bear with us.

@StephC @HGrigsby @Ann-MarieHolloway @Joyce @m.vandun @Adam Higgins @RobW We can inform you this has now been fixed in the latest platform (ESP) build 3416, which is now live in all instances. Kind regards, Nanette

@Ann The build is planned to go live later this week. Many thanks, Nanette.

@Kelvin Great news.

@Kelvin just following up to see how the testing is going?

@Martyn Houghton Sorry to hear this, I can see a support request has been raised. We will follow this up and provide an update as soon as we have one. Kind regards, Nanette.

@7oaks You can configure the request list to include/display the Last update column: Click on the configure/customize the column settings in the Request List view, above highlighted in yellow: There are several other Last Updated columns, should you wish to include them. Many thanks, Nanette

@Martyn Houghton We can confirm that this should be fixed now. The following will need to be done on the ones that aren't working, open affected decision node conditions and resave. Many thanks, Nanette

@Martyn Houghton@Jack_Podmore We are currently investigating this as a potential defect, we will keep you updated as soon as there are any further updates. Many thanks, Nanette.

Hi @Alberto M @Alisha In short, this working as intended, the users will not receive notifications on updates. When a user follows a timeline they should get notified only about updates they have visibility of, we don't send notifications on something they are not allowed to see. Being added as a member gives you access to the details of a request you normally are not allowed to see. However, this does not enable you to receive notifications when you follow the request because you're still not a Member of the team the request is assigned to. This would be an enhancement request, should you wish to request a change in functionality. Nanette.

@Aston Instone Please take the latest Board Manager update from the App Store (click on the update button): Once updated, re-start the process for the request, this should resolve your issue. Many thanks, Nanette.

@Luke Please can you raise a raise with our support team via https://www.hornbill.com/support They will be able to assist with tidying the accounts up and importing the users. Nanette

@Alberto M that's great news.

@Alberto M Thank you for the feedback, we are discussing with our developers. Please bear with us. Many thanks, Nanette

@LifeOfJonny @Martyn Houghton @Danny.M Good news, the above issue has been fixed in this build: Many thanks, Nanette

@Sandip Bhogal We are investigating this with yourself under a support request. Kind regards, Nanette

@LifeOfJonny We are aware of the above issue and are currently investigating, please bear with us. Kind regards, Nanette.

@RobW This is a known defect, which has been fixed in this Service Manager update: Many thanks, Nanette

@Prem Prakash gautam that is correct, it doesn't enforce until a user changes his/her password. At present there isn't the functionality to set a password expiration time limit, for the time being there aren't any immediate plans to implement this. As for the report, you can run a report on the users table, but the password stored there won't be of use because it would be an encrypted value.

@Shamaila Not at the moment, we will be in touch as soon as we have any further update. Many thanks, Nanette

@Paul Alexander @Andrew Tasker We are currently looking into this, we will let you know as soon as there are any further updates. Kind regards, Nanette

@Keith @nasimg @Alberto M We've identified a known defect (KE00161993). We are currently working on fix, we will let you know as soon as there is any further update. Kind regards, Nanette.

@Keith @nasimg@Alberto M We are currently looking into this, please bear with us. Many thanks, Nanette.

@Martyn Houghton @Adrian Simpkins Good news, the change that we have outstanding will include the set message priority option within the email template. This will be available in a future service manager update - keep an eye in the announcements section. Many thanks, Nanette.

Hello @Adam Toms When placing the request on hold, the timers are paused, it allows you to add a reason for why the request is being placed on hold & the time that you wish for it to come off hold. If, the on hold time needs to be changed/extended then the only way to do this, is like you said and is take the request off hold and then place back on hold with a longer date & including the reason why the on hold period has changed. Many thanks, Nanette.