Jump to content

Michael Sharp

Hornbill Users
  • Posts

    665
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by Michael Sharp

  1. @Victor that's correct - I wanted to change that breached/met based on the adjustment of a priority.  Moreso so a report could be presented more accurately (whether negatively or positively).  I'd quite like a button there that only Helpdesk Managers can use to recalculate/adjust the breached/met as I do understand why it isn't a feature for engineers to avoid foul play.

    Regards,

    Mike.

  2. When a response is made on a request and the priority is changed, the SLT and Within Response Time is not overwritten.  I guess the field is not changed in the database?  This feels like a defect to me?  Scenario created as follows:

    1. Request raised with an 8 hour response time (P4 SLA)
    2. Request responded to within 8 hours
    3. Request priority adjusted to P1 SLA (10 minutes response time) - should now be marked as a failed SLA

    image.png.425aef9c39a0f6227ebbba898b290dc9.png

    @Bob Dickinson tested following our discussion earlier

  3. 1 hour ago, Gerry said:

    @Michael Sharp

    Lol :: thanks for posting.  Yes, it seems everyone is ok with it now, as I think I said originally, the change was going to facilitate other things in the future, but also allows many login options that were previously... errr... difficult...

    I assume you have rolled out a combination of direct and SSO logins :)

    Gerry

    Actually migrating SSO from ADFS to Azure so can test both services non-disruptively and also log in as system admin with the direct login to manage....!

    • Like 1
  4. @Bob Dickinson thanks for picking this up, appreciate your time.  ADFS is currently based on-premise for us (working fine) however is a single point of failure for a growing number of applications now (we don't have a clustered service).  Also this requires a further manual login when using SSO outside the network perimeter which has caused issues for what is very much now a remote workforce.  I'm exploring the use of Azure SSO as a more robust/resilient solution which can also enable us to further secure the systems that this authenticates too.

    Will drop you my mobile in a DM which will be the best number to get me on.

    Regards and thanks,

    Mike.

  5. Apologies, didn't know where to camp this request.  I'm having difficulty getting the Azure SSO to work and wondered if you could help please?  Have followed the guide as per:

    https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/hornbill-tutorial#configure-azure-ad-single-sign-on

    Have used the Test single sign on in Azure which appears to work successfully (perhaps a cached authentication though), however getting an error on all other devices when trying to access https://live.hornbill.com/OURDOMAIN as below:

    image.png.e1ca04247479d1863496e4cfd005f208.png

    Please can you help?

    Thanks,

    Mike.

  6. MORE OFTEN than not, we are finding that the request category tab is not visible unless the page is refreshed.  This is when we:

    1. Open a new request
    2. BPM locks all actions except Category and Customer
    3. Immediately after the BPM is set to Wait for Category with the focus on Category

    Image below for clarity:

    image.png.80bf14d8b49b694b429ca538976f3e8d.png

    Please can you help?  At the moment our engineers are refreshing the web page to make this visible so a category can be selected.  This has happened for months but I haven't bothered to report until now!

    Thanks,

    Mike.

  7. 1 hour ago, Bob Dickinson said:

    @Michael Sharp Following on from the "Hidden Service" idea - you could create a team called "Management" or something along those lines where only you are the member. 

    Then in the new hidden service, add this team to the "Supported Teams" section. This means that only you will have visibility of this service and it won't appear as a selectable service for the analysts when they are raising new requests, nor will they have access to open tickets that have been raised against this service. 
    However YOU will still have the ability to link it to existing Incidents and Service Requests as desired, and the request can still be raised against a customer.

    Kind Regards

    Bob

    Thanks @Bob Dickinson I've previously done this but I've been adding my staff to the serviced users when creating requests and removing them again after it's been spun up :)

    Mike.

  8. I've created a VIP list in Hornbill as a General group in Organisation and want to be able to conduct the following:

    • Branch BPMs based on customer membership
    • Configure dashboard tiles to filter requests where users are in this group
    • Configure reports to filter requests where users are in this group

    Seems very straightforward as a concept but struggling to grasp how this can be done?

    Regards,

    Mike.

  9. @Bob Dickinson this was a way of creating a timeline of my staff's quality checks.  For example, I have a request for "staff member A" which I link other requests to it and make comments to refer back to at a later time when conducting reviews of their performance.  Hiding from the portal is one thing, but I wanted to hide these from the engineers I'm managing also :)

    Regards,

    Mike.

×
×
  • Create New...