@danp Looks like that resolved it. Must have written event purely out of habit. FF will be good after the next release.
Posts made by QuixoticJeremy
-
RE: Sodium: Closed ticket in error
-
RE: Sodium Filters / Views
@danp said in Sodium Filters / Views:
@quixoticjeremy Are there plans to allow for specifying a "default" view, configurable by the end-user?
Most of this is going to be revamped anyways and likely we will include more features such as this.
-
RE: Sodium: Closed ticket in error
@danp said in Sodium: Closed ticket in error:
"change input": function(e){ e.preventDefault(); if(event.target.id == 'saveFilasView'){ $("#vn").toggle(); }
Shouldn't
event
be changed toe
? That would likely fix the issue with FF.Very likely. Interesting that it has no issues in chrome (you are the only one having issues in chrome and there are a LOT of people creating filters with no issues in chrome, I am seeing it in firefox now though) yet fails in firefox. When I get a moment today I'll look into it.
-
RE: Sodium Update
@quixoticjustin said in Sodium Update:
Today's first update has just been deployed.
Note to everyone, please log out and back in after this deployment.
-
RE: Sodium Filters / Views
@quixoticjeremy said in Sodium Filters / Views:
@danp said in Sodium Filters / Views:
A couple of observations --
- When none of the Ticket Status checkboxes are checked, only open tickets are shown. I would expect all tickets to be shown.
- Need to be able to update / remove a View. Currently get the following when I try to Save Filter As View with an existing name
- Well look at that on the first point. Will fix that today.
- Valid points. Already on the list of things to do. Hopefully will get to this today as well
First point has been resolved and will be in the next release. Looking to get to the second point here in a little bit.
-
RE: What Are You Doing Right Now
@scottalanmiller said in What Are You Doing Right Now:
Just had a post deleted on SW for pointing out that Windows 7 and Ubuntu 14.04 are pretty old. Not a big deal, but feels a bit over the top. Nothing rude, nothing inappropriate, nothing off topic. Just pointing out to the OP that he's using crazy old technologies that might be contributing to his problems.
Seems a bit ridiculous to me. Win7 is ancient. Mainstream support ended back in 2015 for that....
-
RE: Sodium Ticket Status
@danp said in Sodium Ticket Status:
@quixoticjeremy Appears to only occur under some situations. For example --
- Select a ticket from the upper list
- Edit it, change the status to In Progress, and then save the ticket
At this point, you can click the edit icon and the ticket status is correctly maintained as In Progress. However, if you switch tickets and then come back to the current one before clicking edit, then the incorrect ticket status is shown (Open vs In Progress).
I think I see what is going on now, this is actually a symptom of another issue. Might take a tiny bit to fix but this will get resolved shortly.
-
RE: Sodium Ticket Status
@danp Alright, I'm going to keep trying to repro the issue. I'll keep you posted on this one.
-
RE: Sodium Ticket Status
@danp And this is from any previous status or just one in particular?
edit: (not that I think this would matter but I'm trying to make sure I have the whole picture).
-
RE: Recently Added Tickets Backwards
This issue has been resolved and will be fixed in the next release.
-
RE: Sodium Ticket Status
@danp said in Sodium Ticket Status:
There's an issue with the ticket status getting changed to Open whenever a ticket is edited and then saved.
Interesting. I'm not able to repro the issue yet. What browser are you using?
-
RE: Recently Added Tickets Backwards
This description isn't quite accurate. The orders are correct except the last one added. Look at the date order:
I'll be looking into this but this isn't quite as simple as just swapping the sort order (which is already correct). Something else is going on.
-
RE: Sodium Update
@danp said in Sodium Update:
Appears that the sub-tickets are not being properly loaded in the master ticket.
This is now fixed, will be included in the next release
-
RE: Sodium Update
@danp said in Sodium Update:
Appears that the sub-tickets are not being properly loaded in the master ticket.
Looking into this now.
-
RE: Sodium Update
@danp said in Sodium Update:
@quixoticjustin Like the new dashboard. The confirmation dialog for closing/deleting a ticket is pretty bland. Also, could you make the Close button into a dual purpose one that would allow you to reopen a closed ticket?
I'm glad you like the new dashboard. The closing/deleting dialog will get updated eventually to look more slick. For now it works. As for the close button serving a dual purpose, sure thing.
-
RE: Sodium: Ticket layout
@danp said in Sodium: Ticket layout:
@scottalanmiller said in Sodium: Ticket layout:
Having delete anywhere that people look at it all of the time is probably bad. That's a super special case button that should almost always route to a manager for approval and should be trivially disabled as it often would need to be forbidden.
Along this lines, perhaps this should be a setting under Group Permissions.
This could definitely be a good route to go with this.
-
RE: Sodium: Ticket layout
@gjacobse said in Sodium: Ticket layout:
@quixoticjeremy said in Sodium: Ticket layout:
While I do agree there should be a confirmation, I'll do that up here in a bit. However I don't think I agree with switching the locations. Logistically the locations make more sense like this.
edit: it keeps the commit of the note in the same location with other actions like adding time, attachments etc.
I'm flexible - so that should work. Especially in the case of the 'Delete' Button.
Closing/deleting tickets now require confirmation. That being said, the points everyone is bringing up about deleting tickets being in a separate location are valid points that I'm going to think about how to approach today.
-
RE: Sodium Filters / Views
@danp said in Sodium Filters / Views:
A couple of observations --
- When none of the Ticket Status checkboxes are checked, only open tickets are shown. I would expect all tickets to be shown.
- Need to be able to update / remove a View. Currently get the following when I try to Save Filter As View with an existing name
- Well look at that on the first point. Will fix that today.
- Valid points. Already on the list of things to do. Hopefully will get to this today as well
-
RE: Sodium: Ticket layout
While I do agree there should be a confirmation, I'll do that up here in a bit. However I don't think I agree with switching the locations. Logistically the locations make more sense like this.
edit: it keeps the commit of the note in the same location with other actions like adding time, attachments etc.