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 think that while it would be great, older XenServer is going to be out of scope, at least for a really long time, with Sodium. There are a lot of barriers there and a really small use case. Now the current XenServer might be a different matter. Has anyone looked at that at all?
Yeah, while I had a system available I figured looking to see if it would "just work" made sense. But the version of Python is to old, and it's a huge hassle to get a newer version installed at best.
Time to update to XS 7 and test ;)
Yeah, if I had any way to get my own OS installed it would've already been. Another server at WholeSaleInternet.
They don't let you install an OS there? And they don't keep the ones that they offer updated?
They give you a choice, and they always seem to be a little behind. One big reason why it's only every going to be a home lab environment for me and not a recommended service for any company.
And that would do it, one would need to create 2 files, companyName.txt.j2 and mast.conf.j2 with either variables, or just directly with proper values. If someone is already using Ansible, they should easily be able to do that.
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)).