Sodium release for helpdesk: related tickets, attachments, changed time management, etc.
-
I'm getting very slow ticket list population. It's working, it's just blank for a good five to ten seconds.
-
I added ticket 3 as related to ticket 1. In ticket 1, this shows up in the list like it is a sub-ticket. But it ticket 3, it does not show up at all. If 3 is a sub ticket of 1, this might make sense. But if they are just "related" it should show up the same on both sides, right?
-
Deleting an attachment worked, but did not show up until I reloaded.
-
What Ticket/Helpdesk system is this?
-
@scottalanmiller said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
I'm getting very slow ticket list population. It's working, it's just blank for a good five to ten seconds.
Now that this is in production I'm noticing this too. I'm going to look into this.
-
@scottalanmiller said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
I added ticket 3 as related to ticket 1. In ticket 1, this shows up in the list like it is a sub-ticket. But it ticket 3, it does not show up at all. If 3 is a sub ticket of 1, this might make sense. But if they are just "related" it should show up the same on both sides, right?
So this begs the question of is this a functionality issue or a terminology issue. I've seen people describing what they want as both related or sub ticketing. I tend to lean towards sub ticketing and creating a tree of some kind rather than just related tickets. That's just me though. Even with the tree of some kind I would want to list parent though so that's something I do need to do
-
@scottalanmiller said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
Deleting an attachment worked, but did not show up until I reloaded.
Odd that is something I haven't ran into before. I'll check that out today
-
@quixoticjeremy said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
@scottalanmiller said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
I added ticket 3 as related to ticket 1. In ticket 1, this shows up in the list like it is a sub-ticket. But it ticket 3, it does not show up at all. If 3 is a sub ticket of 1, this might make sense. But if they are just "related" it should show up the same on both sides, right?
So this begs the question of is this a functionality issue or a terminology issue. I've seen people describing what they want as both related or sub ticketing. I tend to lean towards sub ticketing and creating a tree of some kind rather than just related tickets. That's just me though. Even with the tree of some kind I would want to list parent though so that's something I do need to do
Is there a way to do this via tags instead? Cause honestly trying to find a ticket number that had similar issues etc.... well who's going to remember that?
-
@stuartjordan said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
What Ticket/Helpdesk system is this?
Hello there, this is the sodium project. Sodium is an rmm / help desk / variety of other Concepts project that is still in I guess we could even call it an alpha stage. We are using mango lassi as a way to communicate with itpros while we develop this so that at the end of the whole project we actually have a product that people want to use. Later today I'm going to kind of do an intro to sodium post that will lead into how to access it how to create an account and how to start using it. In order to start using it though just so that you are aware of before I do that post if you go to sodium.Waxquixotic.com you can sign up for an account there login. We are very early in the software development stages so it is rough there's no doubt about that but please feel free to get in there and test things out and have fun with it.
-
When closing tickets it would be good to either remove them from the view, or provide a top level status of "Closed".
Color coding the tickets might be useful as well. Low Priority - Yellow, Med Priority - Orange, High Priority - Red.
As a really cool feature it would be nice to have the priority of a ticket go up in scale if no progress has been made to the ticket based on when the ticket was made.
IE Low Priority - Can't Print - Green (24 hour window to fix). If it's been 6 hours and no one has worked on the ticket, or put any comments on it from the IT side, the priority goes up to Orange, In another 6 hours it goes to a Red color.
Automatically adding notes along the way as to why the ticket was escalated.
-
@minion-queen said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
@quixoticjeremy said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
@scottalanmiller said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
I added ticket 3 as related to ticket 1. In ticket 1, this shows up in the list like it is a sub-ticket. But it ticket 3, it does not show up at all. If 3 is a sub ticket of 1, this might make sense. But if they are just "related" it should show up the same on both sides, right?
So this begs the question of is this a functionality issue or a terminology issue. I've seen people describing what they want as both related or sub ticketing. I tend to lean towards sub ticketing and creating a tree of some kind rather than just related tickets. That's just me though. Even with the tree of some kind I would want to list parent though so that's something I do need to do
Is there a way to do this via tags instead? Cause honestly trying to find a ticket number that had similar issues etc.... well who's going to remember that?
We actually have this covered already in a way. Ticket types are defined by the user to begin with (very easily I might add) which essentially makes them tags due to the fact that one of the next things that I need to implement is a filtering system where you can filter by ticket type, description, etc. I think of this tree of child tickets as more of a directly related tickets situation where there may be a parent ticket describing the overall situation of things that need to be done for a variety of machines. Then sub tickets for each machine to make it easier to track.
-
@dustinb3403 said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
When closing tickets it would be good to either remove them from the view, or provide a top level status of "Closed".
Color coding the tickets might be useful as well. Low Priority - Yellow, Med Priority - Orange, High Priority - Red.
As a really cool feature it would be nice to have the priority of a ticket go up in scale if no progress has been made to the ticket based on when the ticket was made.
IE Low Priority - Can't Print - Green (24 hour window to fix). If it's been 6 hours and no one has worked on the ticket, or put any comments on it from the IT side, the priority goes up to Orange, In another 6 hours it goes to a Red color.
Automatically adding notes along the way as to why the ticket was escalated.
Couldn't agree more on most of these points and actually is something that I think about regularly.
-
Removing tickets from view when closed: this will likely happen when I put filtering in place so that people can still view closed tickets until they can search specifically for them.
-
Color coding: I like this, and hadn't thought of it.
-
Priority going up with no progress: I feel like this would need to be an option to be able to turn on or off.
I really like these suggestions though. Duly noted.
-
-
@quixoticjeremy Absolutely an optional flag to auto escalate a ticket.
As for the escalation notes provided, they should only be visible to the IT department and not sent out to the person who created the ticket.
-
@dustinb3403 said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
@quixoticjeremy Absolutely an optional flag to auto escalate a ticket.
As for the escalation notes provided, they should only be visible to the IT department and not sent out to the person who created the ticket.
Why not have this configurable as well. Could might light a fire under the responsible user?
-
Providing the ability to assign a ticket to a team member is also a requirement. This way a manager can track who is completing what, and when someone was assigned to the ticket.
Even if by Email only, they are the owner of the ticket. Of course the ability to reassign a ticket has to be there as well.
-
@quixoticjeremy said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
@dustinb3403 said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
@quixoticjeremy Absolutely an optional flag to auto escalate a ticket.
As for the escalation notes provided, they should only be visible to the IT department and not sent out to the person who created the ticket.
Why not have this configurable as well. Could might light a fire under the responsible user?
I was thinking optional per site, not per ticket. IE. the IT department wants the tickets to auto escalate because of RPO/RTO requirements.
If a ticket is open for days, it causes them to fall out of compliance.
But another IT department doesn't have such a requirement.
-
@dustinb3403 said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
Providing the ability to assign a ticket to a team member is also a requirement. This way a manager can track who is completing what, and when someone was assigned to the ticket.
Even if by Email only, they are the owner of the ticket. Of course the ability to reassign a ticket has to be there as well.
Reassigning tickets is already do able. Assigning to a team is on the project list already.
-
Wooh that just gave me another idea. Of providing an RPO/RTO field that is internal to the department for tracking purposes so a department can track their overall performance and improve / adjust their BIA accordingly.
RTO/RPO: Printers can be down for 3 days as we have others
Actual recovery time: 20 minutes
Recommendation based on Ticket Average: Reduce RTO/RPO -
@dustinb3403 said in Sodium release for helpdesk: related tickets, attachments, changed time management, etc.:
Wooh that just gave me another idea. Of providing an RPO/RTO field that is internal to the department for tracking purposes so a department can track their overall performance and improve / adjust their BIA accordingly.
RTO/RPO: Printers can be down for 3 days as we have others
Actual recovery time: 20 minutes
Recommendation based on Ticket Average: Reduce RTO/RPONow that's a cool feature but likely going to come in down the road a ways.
-
The general idea behind the RTO/RPO is once a business has this, they can actively track their performance of being able to resolve problems within their objectives.
Might be overkill and a lot of processing for it. But they'd put in their general objectives in Minutes, Hours, Days etc and then assign a ticket to it that RTO/RPO and proceed to fix the issue.
