@dashrender said in SodiumSuite Helpdesk Time:

@dbeato said in SodiumSuite Helpdesk Time:

IN NJ for example I can bill by the minute, I used to bill in 8 or 12 minutes increments.

Seems arbitrary - did you have a reason for that?
I bill clients on the 15 min, have to include the transition time they are costing me.

It's all arbitrary.

@dashrender said in SodiumSuite Helpdesk Emails:

Are they really?
It's possible they are using gmail as a relay, it's also possible they email direct, but that Send From is just listed as his address.

Definitely things to look into for SPF related blocking, etc.

Nothing is blocked 😞 so I see it is directly.

@quixoticjeremy said in Sodium Suite Asset Management:

@dbeato Lot's of good stuff here. I've been in a bit of a transition (had to make some changes so that I actually had money to pay the bills) so that slowed how quickly I was pumping out fixes but I think we're getting to a point where I'm almost back on track. I'll be looking into all these hopefully later today.

I definitely understand that! Just getting it out there what I found out.

Adding @Sodium @QuixoticJeremy

@jaredbusch said in Sodium: Session Timed sign out:

@quixoticjeremy said in Sodium: Session Timed sign out:

@gjacobse said in Sodium: Session Timed
sign out:

@Sodium has come a long way in the last few months. But currently with the 20 minute signout - it's not something I can really use. It's just really impractical for me to return from addressing a issue after 15 - 20 minutes and have to sign in again...

Duly noted. This was a security choice but as this is not the first time I've heard this we will be looking into changing this.

Don’t choose for me. Give me a remember me button that makes it last 24 hours at a minimum. Keep 20 minutes if you want for those that don’t check it.

This a Chrome-esque disaster. You can recommend all you want, but you cannot force me to do something. I will si ply not use you.

I think you're absolutely right. It all needs to simply be options to select from.

I have been active or busy enough that it may be an hour or so between times I’m in Sodium.

While yesterday was abnormal, I hardly had time to cycle through pages in Sodium...

I hunk I managed something on the order of about +125 emails.

And while I know we are still very much in the infancy stages, sign in for me is rather slow,.. so once kicked- I skip getting back in for another 30-60 minutes due to keeping up with issues

@gjacobse said in Ticket Hash Issues:

@gjacobse said in Ticket Hash Issues:

@gjacobse said in Ticket Hash Issues:

@scottalanmiller said in Ticket Hash Issues:

This is a new issue today...

0_1506548337365_DeepinScreenshot_select-area_20170927163840.png

This is some weird data from the helpdesk. What's up here?

@Sodium

Is that in the Helpdesk? I don't see that.

0_1506551696437_Screenshot (9).png

Ugh,.. well I now stand corrected. Seems I'm now getting teh same thing.

So on timing ... between the time I posted that,.. and now, I've been kicked out... on both FF and Chrome.

Probably because of the deployment that posted on the other thread.

@scottalanmiller Thanks. Thought I had done that, lol.

@gjacobse said in Sodium: Custom Ticket Views:

@danp said in Sodium: Custom Ticket Views:

@quixoticjeremy said in Sodium: Custom Ticket Views:

that being said it's being worked on from the standpoint of logins should timeout ....overnight.... so you should have to login in the morning anyways.

Has this change been pushed out? FWIW, I didn't get auto-logged out overnight.

I dont' get auto-logged out either.

No one does yet.

@quixoticjeremy said in Sodium Helpdesk: Username Using Email Address Cannot Login:

I have been able to create an account using an email as the user name and log in with it. Can you confirm this is now working @NashBrydges ?

Confirmed. I can log in with an email address as a username.

@quixoticjeremy said in Sodium Helpdesk: New Group Permissions Not Working:

From what I can tell this is now working as intended. Can you confirm @NashBrydges ?

Confirmed fixed.

@nashbrydges said in Sodium Helpdesk: Unable To Create Password In Chrome:

@sodium said in Sodium Helpdesk: Unable To Create Password In Chrome:

@quixoticjeremy said in Sodium Helpdesk: Unable To Create Password In Chrome:

Have found the issue and have pushed a release. Keeping an eye for when it hits production to verify that like in dev this will fix the issue.

Push to prod is done.

Confirmed. The fix allows me to create password in Chrome.

Glad to hear, I've moved one of your next bugs. I'll be keeping you posted as soon as I'm rolling it out and as to which one it is.

Looks to be working now.

@ntggene said in Sodium: Open new ticket:

@quixoticjeremy said in Sodium: Open new ticket:

@gjacobse said in Sodium: Open new ticket:

@quixoticjeremy said in Sodium: Open new ticket:

@gjacobse said in Sodium: Open new ticket:

@quixoticjeremy said in Sodium: Open new ticket:

@gjacobse said in Sodium: Open new ticket:

@quixoticjeremy said in Sodium: Open new ticket:

@gjacobse said in Sodium: Open new ticket:

Should there be a Submit button?

0_1501780499893_Selection_057.png

Why in the world is your submit button above your description box....

Ah uhm. well,.. uh.. Are you saying the New Ticket bar is the submit button?

No. Look at your screenshot, right under due date.

Oh - well. yea,.. there it is. Huh.

What browser are you using?

Firefox

LOL gene what did you do! I'm in firefox now, I'm playing with screensize, I'm doing everything and I can't replicate this....

Who me? (innocent look)

Looks find in Chrome - but can move things around (whopps) resetting the browser sets it back. Reset Firefox (54.0.1) reset the page settings and the Submit button is at the bottom now.

Good deal 🙂 I'm still going to look into what went on in there. I know that there is also an active bug right now where datepicker will just stop working.... so if that happens just manually enter the date.

@manxam said in Sodium Storage NaN Bug:

The strange part is that mine has been fine all day. Previously I was seeing either a duplicate 😄 or "Not available" "NaN".

Today? just E: and 😄

Awesome! That is actually not so strange as I did clear up some storage issues. Scott's issue is likely completely unrelated to yours. Yours was cleared up as I reconstructed how we were storing our data. As soon as I did that your issue was resolved (it was the driving force behind the change but it is a huge upgrade to our backend so it was needed). As for Scott's issue, this is an issue with what is being sent to us from the agent. The last line is actually the return code which I just need to filter out, that's nothing. However the D drive not showing it's information is intriguing. The agent obviously couldn't get a read on the drive. I'll be looking into this one later today.