Jump to content

Search the Community

Showing results for tags 'resolve'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Hornbill Platform and Applications
    • OpenForWork
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
    • GRC Manager
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start








Website URL





Found 15 results

  1. Can we request the ability to use Snippets in the Bulk Actions Update and Resolve activities, to mirror the capability for identical actions on individual requests. Cheers Martyn
  2. At the moment if you want to close a bulk number of requests you have to update them to Resolved so that you can populate the resolution text and closure category, and then select them again for another Bulk Action to close them. Can we request a combined Resolve and Close action to allow the setting of the Resolution Text and Closure Region plus then updates the status to Resolved and then subsequently Closed, in one bulk action. Cheers Martyn
  3. https://wiki.hornbill.com/index.php?title=Service_Manager_Business_Process_Workflow#Request_Timers Hi, This forum was particularly helpful with another config change query I had, I was hoping to everyone's brains again? Request Timers; we've recently looked to apply this new enhancement via Application Settings, we have looked to pause the timer on resolve, restart the timer on re-open or end timer on close. We've however found that calls that have been resolved, though they appear as paused seem to also show as 'Timer ongoing' and don't seem to end on close. Our BPM's conditions for resolution timers are: • We do not mark the Resolve Timer as complete – it marks automatically when the call is resolved. • We have chosen to mark the response timer as complete when an analyst is assigned to the call. This is not the same as when the customer is contacted but does give us a measure of how quickly calls are picked up and assessed. Via the Application Settings i understand that only one of either pause on resolve or stop on close can be enable. Will we need to make changes to our BPM to be able to pause the timer on resolve and also have it continue if it gets reopened? Regards Rashid MKC
  4. Can we request an enhancement to the 'Linked Request' BPM node, in that there is an option to limit which linked requests are updated by request type. In our scenario we are implementing Problem Management and will want to use the node to update/resolve the Incidents linked to the Problem request. However there may be other Problem, Release, Change, Known Errors etc linked to the same request which we would not want to update/resolve. Therefore can we ask for the filter option on both Update and Resolve Linked Requests so that it can be done by 'Request Type', i.e. we need to be a bit more precise in only updating the linked incidents and not everything else it may be related to. Cheers Martyn
  5. Hi We've received some feedback from our analysts that the "Resolve Linked Requests" drop-down on the "Resolve" tab isn't obvious enough, and I can't help but agree. We've unfortunately seen several critical incidents be resolved by analysts then child incidents remain open for some time, causing a breach. Obviously some of this can be avoided with training. When resolving a critical or high priority incident, it is likely that child incidents will be associated and therefore need resolving at the same time as the parent incident. Similar to the "Reopen" and "Edit" button, could an additional button be added that says "Resolve Linked Requests" (preferably next to "Close")? The reason we cannot use the "Resolve Linked Requests" node in the business process, is because often a parent incident will have a problem, known error or change request associated which we do not want resolving at the same time as the incident. Thanks Lauren
  6. If we are seeing a common issue within the company we normally raise a problem or known error and associate all the relevant calls that have been logged to them. When we close that problem or known error is there a way for users of all the calls that have been associated to be emailed the resolution? Not sure if this in existence, if not it would be very useful as did exist in Support Works.
  7. Hi We've found that some of our requests are being resolved by analysts without a priority being set - despite there being a mandatory checkpoint to set a priority. We've located a setting to stop a request being resolved/closed without an owner, but no similar setting for the priority. Is there a setting to prevent the resolution of requests that do not have a priority set? We've thought about locked buttons, but unfortunately they don't fit our varying incident types. Thanks Lauren
  8. At the moment with the Update Request Status node you can update the status of a service manage request to Resolved or Closed, but the node does not support the ability to pass in as a literal or variable the Resolution Text or Category values. It would be useful to be able to do this from within the BPM and not rely on a manual activity. Similarly it would be could to be able to do this for Cancel as well, passing the cancellation description. Cheers Martyn
  9. We ran the latest update this morning and have noticed that the resolve action is not appearing for some users. The process shows the hide resolved action followed by the show resolved action but the teams don't see the button. This is on a variety of processes and affecting different teams. I can see the resolve button I guess this is because I am an admin. Can someone help or should this be logged as an incident? Helen
  10. Hi all I'm hoping someone will be able to provide guidance on this one. I'm looking to create a Widget displaying the Average Resolution time of our Incidents. Using the demo data I copied the measure that the widget would be using as it's data source and believe it is working. The issue however is that the average time that it has calculated for November is drastically higher than expected. Due to this, I am guessing that the timer counts the seconds between 'h_datelogged' and 'h_fixtime' without taking our working hours or 'on hold' statuses into account? Have I got the wrong impression with this or is there a way to make it take the above into consideration? Summary: I'd like to know the Average amount of time (using the SLA counter that is paused when out of office hours or on hold) an Incident was either 'New' or 'Open' before it was resolved. Here is the Measure I've got: Thanks in advance for any help! Drew
  11. Hi all, I have come across some strange behaviour in our instance where by a couple of analysts (at least) can still resolve calls even though the resolve button is locked. Neither of them have admin roles at all. The roles they have assigned are as attached (as are the settings of the 2 custom roles) Any ideas?
  12. Afternoont, I have run a report for our P1's to find out the Resolve times for them. The report is as follows: The IN shows as: So it has been logged - responded to and Resolved and closed - Response time is reporting correctly however when i run a report for these figures it is showing a Resolution time of 115200 which is about 1920 Minutes, which equates to 32 hours? Now from what I can see from when it was logged to when it was resolved from the call itself it only took 5 hours 49-50ish minutes? so why on earth is it reporting as 32 hours? Please also note that @ 9.04am it was raised from a p3 to a p1 is it getting confused because of this? please help!
  13. Morning all, Im running a report to find out our resolve times for calls and a average... Firstly the only resolve figure i can find is in seconds? I dont really get what the Resolve time means as it reads in just numbers. or what the Resolution Timer ID is either? Also is their a way to work out a average on a report? Thanks Hayley
  14. Good afternoon everyone, Another quick question. None of our users have the right to resolve calls currently other than me admin, manager and Team leader of service desk. Do we know what role this sits under? and is there a safe role for this (So as not to give users too many permissions) Many thanks as always Hayley.
  15. We have started to use the Hornbill Mobile App on both Android and IOS mobile phones. Whilst its a fantastic way for our ITC Engineers to update their calls whilst working in the field they are not able to resolve them. Are there any plans for this facility to be added to the mobile app and if so any idea when it might happen. Many thanks Gill Forum Admin Edit: The functionality was provided in one of the earlier Service Manager builds. This thread is now locked.
  • Create New...