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.
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 Function.Template._withTemplateInstanceFunc (https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:714:12)
at Object.Spacebars.call (https://sodium.waxquixotic.com/packages/spacebars.js?hash=ebf9381e7fc625d41acb0df14995b7614360858a:14:14)
at Blaze.View.<anonymous> (https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:172:181)
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.
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.
Good idea, maybe direct links to different sections as well so that they can be opened directly and saved as default pages or whatever. Different people will want to start with different numbers of tabs and at different points.
Cool.. I tried the Scroll wheel click to open in new tab and that didn't work... which is a separate issue,.. but ...
Avatars are pretty cool. It immediately makes the whole thing feel more polished, for one. But it also means that a lot of times you can shrink things and use little avatars to clean up screen real estate to make things easier.
Yep and that's definitely the direction this will head. This release in particular was just getting the foundation of avatars in place but it will be used all over the place eventually.
I would think not changing the organization of the ticket would be a good thing in most cases.
Add an option, but also a confirmation.
Are you sure you want to change this tickets Org to " "?
"Most cases." Problem is, if there are any cases, it needs to be able to be changed. You don't want ticket data going to the wrong entity. I can't think of any case where it would be okay to be locked.
That was my point, allow the change, but confirm it before it's set. You don't want a ticket getting moved from one org to another org with sensitive information in it, by mistake.
I have completed working on this for now. Moving forward if there is a delay in check in and your machine is on, treat like a bug and contact me.
Looking good here.
Perfect, server just went down briefly for another very small release (idiotic me forgot to move the logging level back down so I was getting spammed with information I don't need as I monitor the server (yes this needs to be changable but atm is hardcoded)).