@nadnerb said in SodiumSuite: Close account:

I ended up deleting the admin account, so there's zero accounts in it now.

I was kind of hoping that it'd complain about deleting the only account and put up a bit more of a fight. Perhaps with one of those "Contact support to remove this account" messages or at least have some documentation available.

Interesting, will have to look into how that cascades.

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

Well yes, but also looking for some 3rd party application upgrade options. IE adobe reader etc.

@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.

I think using a different term than Agent here makes more sense. I don't want to manage Agents, but Assets. Once there are non-agent entities that need to be grouped, this will be all the more confusing.

@quixoticjustin said in Sodium: Apply Updates:

Yeah, lots of cleaning up needed for the patch system. It is early and mostly works, but leaves a lot to be desired yet 🙂

We are working on a design for a patching dashboard that will give a lot more power specifically around patching.

Exactly, not a lot going to be fixed up on the way it looks currently when a lot of work is going to be going into this in the near future to give a lot more functionality.

@quixoticjeremy said in Salt Question:

@stacksofplates Likely no, our checkins are done via our own scheduling. Would not think that altering that would effect us.

Ah ok. Sounds good.

Hopefully soon-ish there will be workflows for things like ticket closings so that there can be customer defined actions, checks, or whatever when something like that happens.

Long term, as Jeremy implies, loads of filters and views are expected, everywhere in the system. It's not at the top of the list, but it gets higher and higher all of the time as it impacts a lot of basic usability. The system is heavily designed around filters and views being key components of how it all works, both user accessible and behind the scenes.

For example, we want to easily support use by normal users, individual companies, consultants and MSPs. But we don't want to the system to actually work differently, just look different for different people. For example, individual home users likely don't even want to know that there is ticketing. But an MSP might want is very much in the forefront. It will be a view engine making that all possible.

We think that the issue was tied to performance. We saw the system being driven really hard, there is a lot going on behind the scenes. Our infrastructure upgrade this morning seems to have addressed the issue well.

@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.

@danp said in Sodium --:

Just checked in Chrome and I get this --

Exception in template helper: TypeError: Cannot read property 'company' of undefined at Object.unitGroups (https://sodium.waxquixotic.com/app.js?hash=9a69b28b89efe0a1f976612c19bd1154b5baa7e4:1656:35) at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:185:18 at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:112:41 at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:191:182 at Function.Template._withTemplateInstanceFunc (https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:714:12) at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:191:74 at Object.Spacebars.call (https://sodium.waxquixotic.com/packages/spacebars.js?hash=ebf9381e7fc625d41acb0df14995b7614360858a:14:14) at https://sodium.waxquixotic.com/app.js?hash=9a69b28b89efe0a1f976612c19bd1154b5baa7e4:1:31142 at Blaze.View.<anonymous> (https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:172:181) at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:120:252

That's just initial load. Won't effect anything. the client side threw that error before it read from the server side subscription. I just don't have a catch wrapped around it yet. Not a big deal.

@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.

This issue has been resolved and will be fixed in the next release.

@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.

Sounds like a solid enough plan. @QuixoticJeremy

Tagging @Sodium

@nerdydad said in SodiumSuite Pricing Model:

Like...free forever, no restrictions? How are you going to monetize this? Ads such as ML?

Discussed has been ads and extra services such as logging.

Any chance to add the Del View on Helpdesk:

0_1504724389024_2017-09-06 14_57_51-Sodium.png

0_1504724420956_2017-09-06 14_58_16-Sodium.png