Sean Burke

My feedback

  1. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SMA (K1000) » Service Desk  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Burke shared this idea  · 
  2. 668 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  SMA (K1000) » Asset Management  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Dean Wade responded

    Our thoughts on this feature are evolving. The ability to construct a floor map, plot different objects (people, printers, fire extinguisher, etc) and have links back into the asset management module are all concepts we are starting to think through. This will be a longer term deliverable but please continue providing your feedback.

    Sean Burke commented  · 

    This would also be great if you could put users on the map as well, or if the map also showed you the user's name next to the physical asset. So if I had an employee called John Doe tied to a computer XYZ, There would be a picture of a computer with the computer name XYX and maybe you could tie a photo to a user. That way you know the name of there user whose computer you're going to with a picture of them for easy reference.

  3. 428 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  SMA (K1000) » Service Desk  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Burke commented  · 

    I agree. To expand on this, I think there should be a true parent-child relationship for the tickets that are spawned. For example, Dell implements Stages where items at each stage need to all be completed before you move to the next stage. Although I see why this might be useful, I think a better implementation would be a parent ticket followed by child tickets which can also have children, etc. So if for example you have a new hire workflow, a user selects AD Account Needed from a drop down within the parent ticket, either yes or no. If they select yes, a child ticket is spawned to create an AD account (and, like suggested, passes certain information such as the name, department, telephone number, etc to the child ticket).

    Sean Burke supported this idea  · 

Feedback and Knowledge Base