Interesting problem with preferences

While looking at, playing with and working out the kinks of our new,
(hopefully) soon to be live server, a user found something interesting.
He was attempting to change his preferrences for “My Tickets” under RT
at a glance. The specific change was to add a column to the “Show
Columns” list.

This change resulted in successfully adding the column to the list.
However, the unexpected result is the loss of his ability to view the
tickets he owns on the home page. The title bar is there with all the
column headers, but no tickets.

This has been repeated using other users, new tickets and other
settings. For example, by changing the “Order by:” option to something
and saving, the same result is achieved. In addition, after any change
is saved, the “Order by:” list is reset with AdminCc.EmailAddress as the
setting to order by. This cannot be changed as it merely resets.

Has this been experienced by others? How can I fix it?

Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps

While looking at, playing with and working out the kinks of our new,
(hopefully) soon to be live server, a user found something interesting.
He was attempting to change his preferrences for “My Tickets” under RT
at a glance. The specific change was to add a column to the “Show
Columns” list.

Nobody will be able to help you unless you tell them that you’re running
RT 3.6.0pre1.

Jesse Vincent wrote:

Jesse Vincent wrote:

While looking at, playing with and working out the kinks of our new,
(hopefully) soon to be live server, a user found something interesting.
He was attempting to change his preferrences for “My Tickets” under RT
at a glance. The specific change was to add a column to the “Show
Columns” list.
Nobody will be able to help you unless you tell them that you’re running
RT 3.6.0pre1.

Are you saying I SHOULD be using 3.6.0pre1? I ask because the version
I’m referring to is 3.5.7. I added this info in a second posting when I
realized I forgot it in the first.

Well, 3.5.7 was a random developer snapshot along the way to 3.6. And
we’ve fixed a whole lot of bugs since then. (If you’d been reading the
lists closely, you’d have seen others report this bug and confirm that
we fixed it in 3.6.0pre1.) So yeah, I’m pretty sure that you shouldn’t be
running 3.5.7 in production. And also pretty sure that 3.6.0pre1 will
treat you better. But it’s certainly not something we’ve called
production ready yet. We’re waiting for a bit more of your feedback
before we do.

Ah…

Assuming I use 3.6.0pre1 instead, are all the css files transferrable?
Are there changes to them that might make it difficult to swap over?

Ah…

Assuming I use 3.6.0pre1 instead, are all the css files transferrable?

I believe so

Are there changes to them that might make it difficult to swap over?

Not to my knowledge. How much have you customized 3.5.x’s look and feel?
I’m sure there are others out there who would love to see what you’ve
done.

Jesse Vincent wrote:

Ah…

Assuming I use 3.6.0pre1 instead, are all the css files transferrable?

I believe so

Are there changes to them that might make it difficult to swap over?

Not to my knowledge. How much have you customized 3.5.x’s look and feel?
I’m sure there are others out there who would love to see what you’ve
done.
r

Don’t give me too much credit. I’ve merely changed the color scheme.
Otherwise it looks the same.

Does this bug exist in 3.4.5?

Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps

Jesse Vincent wrote: