ArmandoDM

Hi @Paul Alexander if you made the new managers the new service's owner and they have Services Manager rights, then they should be able to update the service description. Can you please double check that the service ownership has been passed on the new heads of department ? Regards Armando

Hi @Ann-MarieHolloway, as @James Ainsworthmentioned, the fix will be available in the next Service Manager update. Because of the nature of the defect, for the fix to be applied you need to re-create the chart after taking the next update. Regards Armando

Hi @Ann-MarieHolloway apologies for the inconvenience. I will report this issue to the relevant team for investigation. Regards Armando

Hi @Adrian Simpkins, @Martyn Houghton apologies for the inconvenience. The issue has been addressed, and the fix will be available with the next major Service Manager build. Regards Armando

Hi @Francis von Stein if you specify that a field must be unique, then you will be prevented from creating a new asset which would be a 'duplicate'. There will be validation. The validation should be per Asset Type. However you try to import/add/update an asset, there will be a validation on the unique fields defined on each asset: if you try to add a duplicate, the action will fail. Hope this makes sense? Regards Armando

Hi @Francis von Stein at the moment there is no validation about duplicate names, but we have a story on the pipeline to let you specify unique fields on assets in order to prevent duplicates. As far the list of 'State' and 'Operational State', I will mention your requirement to the relevant people and get back to you. Regards Armando

Hi @Nikolaj the post is automatically dismissed if the user has the request open already, which is the case I can see in the screenshot. As far the notifications, if you assign a request to an analyst, then only the analyst will receive the notification, unless he's assigning it to himself. In this case the team is not supposed to receive any notification. The team will receive a notification only when the request is assigned to a team (with no analyst). If you assign a request to an analyst, or change the analyst, then only the analyst is supposed to be notified, not the Team Hope this makes sense ? Regards Armando

Hi @Nikolaj We could not replicate this issue. A new build has just been released. could you please update and try again and see if the issue still persists ? Regards Armando

Hi @Nikolaj thank you for mentioning this. I reported this problem for investigation. Will keep you updated Thanks Armando

Hi @Nikolaj Can you please give an example where the email notification is not sent? Thank you Armando

Hi @Nikolaj I will report this issue for investigation. Will get back to you ASAP. Can you please give an example where the email notification is not sent? Ideally we would like to replicate the issue. Regards Armando

Hi @Nikolaj we are not aware of any issue with the notifications. Can you please double check a few things? 1. which notification type in set in the admin ? 2. if the per-user notification is enabled (see app-etting guest.app.requests.notification.allowUserDefinedNotificationType) , then you should also look at your profile page and check your personal settings 3. check if the email template set in the admin is set and it exists. Regards Armando

Thank you for the update @HHH, @Frank Reay @Paul Alexander can you please clear the browser cache and try again , and tell if the issue still persists ? Regards Armando

Hi @Paul Alexander, @Frank Reay, @HHH can you confirm that the issue is not because of the default visibility applied to the attachments please? Thanks Armando

Hi @Paul Alexander, @Frank Reay I will report this issue for investigation. Regards Armando

Hi @HHH, @Paul Alexander may I ask if you are running the latest update of Service Manager and which browser you're using? Regards Armando

Hi @Alisha the value 'h_impact' is actually populated following an impact assessment on the request, if configured in the relevant BPM operation. Regards Armando

Hi @David Longley also, the services and the catalogs displayed depend on a number of conditions for service details form in PCF. You can see more details here: https://wiki.hornbill.com/index.php/Progressive_Capture_Workflow Hope that helps regards Armando

Hi @samwoo apologies for the late response. Thank you for bringing this issue to our attention. We are working to fix it; the fix will be delivered with the next Service Manager build. Regards Armando

Hi @samwoo , yes I read it and I will mention it. Regards Armando

No worries @samwoo, happy to help. I will mention your suggestion as a possible enhancement. Thank you Armando

Hi @samwoo is there any user enabled for assignment ?

Hi @samwoo the teams displayed are only the ones supporting the service the request is raised against, so if the request has no Service then you should see all team. Unless all members of a team are disabled for assignment. Can you please check that the teams missing have at least a member enabled to assignment? Regards Armando

Hi @samwoo we should be good I think. Let me just double check with the relevant people they are happy with it. Regards Armando

Hi @Jamie Talbot you may raise the Change Requests as a linked request , starting from the Service Request page, as per screenshot. This way, summary and description are automatically populated. Regards Armando