Add queue change to Update.html (comment/reply) & CF Columns under Basic view

Hi,

Change queue during comment/reply (on Update.html)

I’m wondering of there’s an easy way of adding Queue change to the
comment/reply page (Update.html).

It would be a nice addition to habe the ability to enable/disable this. We
have several departments that communicate with each other, having the
ability to change the queue when placing a comment/reply would help with
the communication (easier then placing the comment and then changing the
queue via Basics, or easier then using the Jumbo page.

The reason I’m asking is because I want to stay away from editing these
files (they break on updates ^_~), I’d like a more general solution which
will persist during updates. (same goes for the next question)

CustomField Single column view under Basics

Also, I’ve found this plugin (thanks Rus!)
RT::Extension::CustomFieldsOnUpdate (
RT::Extension::CustomFieldsOnUpdate - edit ticket's custom fields on reply/comment - metacpan.org)
The plugin works great but the order in which the CustomFields are shown is
kinda messy. The reason for the order being messy is because we’ve set the
order based upon the two column view under Basics. (which goes from right
to left and then from top to down)

In the RT Config there’s this option which should make it possible to show
a single column view of the Custom Fields:

=item C<$EditCustomFieldsSingleColumn>

When displaying a list of Ticket Custom Fields for editing, RT
defaults to a 2 column list. If you set this to 1, it will instead
display the Custom Fields in a single column.
=cut
Set($EditCustomFieldsSingleColumn, 0);

This option however doesn’t seem to have any effect.

Will this option get a fix during a future release?

This would be great, if I can display the CustomFields in a single column
on all pages then I can have a uniform CF order which will be the same on
the Ticket overview, basics and comment/reply page. (or any other tip to
achieve this would be appreciated)

– Bart

Change queue during comment/reply (on Update.html)
I’m wondering of there’s an easy way of adding Queue change to the comment/reply page
(Update.html).
It would be a nice addition to habe the ability to enable/disable this. We have several
departments that communicate with each other, having the ability to change the queue when
placing a comment/reply would help with the communication (easier then placing the comment and
then changing the queue via Basics, or easier then using the Jumbo page.
The reason I’m asking is because I want to stay away from editing these files (they break on
updates ^_~), I’d like a more general solution which will persist during updates. (same goes
for the next question)

You want to read about Callbacks on the wiki, or look at how the
extension you link to is doing it and borrow the idea. You should be
able to add the SelectQueue component and then it’ll get processed
during the normal update process.

CustomField Single column view under Basics
Also, I’ve found this plugin (thanks Rus!) RT::Extension::CustomFieldsOnUpdate (
[1]RT::Extension::CustomFieldsOnUpdate - edit ticket's custom fields on reply/comment - metacpan.org
)
The plugin works great but the order in which the CustomFields are shown is kinda messy. The
reason for the order being messy is because we’ve set the order based upon the two column view
under Basics. (which goes from right to left and then from top to down)
In the RT Config there’s this option which should make it possible to show a single column
view of the Custom Fields:

 =item C<$EditCustomFieldsSingleColumn>
 When displaying a list of Ticket Custom Fields for editing, RT
 defaults to a 2 column list. If you set this to 1, it will instead
 display the Custom Fields in a single column.
 =cut
 Set($EditCustomFieldsSingleColumn, 0);

This option however doesn’t seem to have any effect.
Will this option get a fix during a future release?

There’s a bug open for this, unfortunately it was broken during the
rewrite of the Update page and lost in the merge up from 3.8 to 4.0
(the option works in 3.8 where it was implemented). You can track the
bug here

http://issues.bestpractical.com/Ticket/Display.html?id=18555

-kevin