Wiki update request: QuickResolveandQuickReject (for rt4)

RT Users
1

Hi All,

We had a flawless upgrade from 3.8.8 to 4.0.1 this week (thanks to
BestPractial and the Debian package maintainers).

Some of our users have requested the QuickResolveandQuickReject
addition:

http://requesttracker.wikia.com/wiki/QuickResolveandQuickReject

Has anyone sorted out what needs to change to make this work with rt4?

Ben

PGP (318B6A97): 3F23 EBC8 B73E 92B7 0A67 705A 8219 DCF0 318B 6A97

signature.asc (828 Bytes)

2

Hi All,

We had a flawless upgrade from 3.8.8 to 4.0.1 this week (thanks to
BestPractial and the Debian package maintainers).

Some of our users have requested the QuickResolveandQuickReject
addition:

http://requesttracker.wikia.com/wiki/QuickResolveandQuickReject

Has anyone sorted out what needs to change to make this work with rt4?

You can do both of those with the included Lifecycles functionality.

Read about it in RT_Config.pm and copy your lifecycles over to
RT_SiteConfig.pm to add the new transitions

-kevin

3

Hi All,

We had a flawless upgrade from 3.8.8 to 4.0.1 this week (thanks to
BestPractial and the Debian package maintainers).

Some of our users have requested the QuickResolveandQuickReject
addition:

http://requesttracker.wikia.com/wiki/QuickResolveandQuickReject

Has anyone sorted out what needs to change to make this work with rt4?

You can do both of those with the included Lifecycles functionality.

Read about it in RT_Config.pm and copy your lifecycles over to
RT_SiteConfig.pm to add the new transitions

Hmm. I’ve read about it, and I’ve copied over the default %Lifecycles
into RT_SiteConfig.pm, adding this action to “default”:

'open -> resolved' => { label => 'Quick Resolve' },

…right below the default “Resolve” action, and restarted apache (using
mod_perl), but I don’t see a new “Quick Resolve” item in the action menu
in the web ui.

Obviously I’m missing something.

Ben

PGP (318B6A97): 3F23 EBC8 B73E 92B7 0A67 705A 8219 DCF0 318B 6A97

signature.asc (828 Bytes)

4

Hi All,

We had a flawless upgrade from 3.8.8 to 4.0.1 this week (thanks to
BestPractial and the Debian package maintainers).

Some of our users have requested the QuickResolveandQuickReject
addition:

http://requesttracker.wikia.com/wiki/QuickResolveandQuickReject

Has anyone sorted out what needs to change to make this work with rt4?

You can do both of those with the included Lifecycles functionality.

Read about it in RT_Config.pm and copy your lifecycles over to
RT_SiteConfig.pm to add the new transitions

Hmm. I’ve read about it, and I’ve copied over the default %Lifecycles
into RT_SiteConfig.pm, adding this action to “default”:

'open -> resolved' => { label => 'Quick Resolve' },

…right below the default “Resolve” action, and restarted apache (using
mod_perl), but I don’t see a new “Quick Resolve” item in the action menu
in the web ui.

Obviously I’m missing something.

Is the ticket you’re testing new or open?

-kevin

5

On Fri, Aug 05, 2011 at 11:33:12AM -0700, Ben Poliakoff wrote:

Hi All,

We had a flawless upgrade from 3.8.8 to 4.0.1 this week (thanks to
BestPractial and the Debian package maintainers).

Some of our users have requested the QuickResolveandQuickReject
addition:

http://requesttracker.wikia.com/wiki/QuickResolveandQuickReject

Has anyone sorted out what needs to change to make this work with rt4?

You can do both of those with the included Lifecycles functionality.

Read about it in RT_Config.pm and copy your lifecycles over to
RT_SiteConfig.pm to add the new transitions

Hmm. I’ve read about it, and I’ve copied over the default %Lifecycles
into RT_SiteConfig.pm, adding this action to “default”:

'open -> resolved' => { label => 'Quick Resolve' },

…right below the default “Resolve” action, and restarted apache (using
mod_perl), but I don’t see a new “Quick Resolve” item in the action menu
in the web ui.

Obviously I’m missing something.

Is the ticket you’re testing new or open?

I appreciate your spotting what should have been obvious to me: the
ticket status was new, so consequently the “Quick Resolve” action wasn’t
in the menu. Once the status was set to open “Quick Resolve” was
available and worked as it should. I’ll update the wiki page to reflect
this.

Thanks much for your help,

Ben

PGP (318B6A97): 3F23 EBC8 B73E 92B7 0A67 705A 8219 DCF0 318B 6A97

signature.asc (828 Bytes)

6

Hi All,

We had a flawless upgrade from 3.8.8 to 4.0.1 this week (thanks to
BestPractial and the Debian package maintainers).

Some of our users have requested the QuickResolveandQuickReject
addition:

http://requesttracker.wikia.com/wiki/QuickResolveandQuickReject

Has anyone sorted out what needs to change to make this work with rt4?

You can do both of those with the included Lifecycles functionality.

Read about it in RT_Config.pm and copy your lifecycles over to
RT_SiteConfig.pm to add the new transitions

Hmm. I’ve read about it, and I’ve copied over the default %Lifecycles
into RT_SiteConfig.pm, adding this action to “default”:

'open -> resolved' => { label => 'Quick Resolve' },

…right below the default “Resolve” action, and restarted apache (using
mod_perl), but I don’t see a new “Quick Resolve” item in the action menu
in the web ui.

Obviously I’m missing something.

Is the ticket you’re testing new or open?

I appreciate your spotting what should have been obvious to me: the
ticket status was new, so consequently the “Quick Resolve” action wasn’t
in the menu. Once the status was set to open “Quick Resolve” was
available and worked as it should. I’ll update the wiki page to reflect
this.

It’s obvious because I made the same error while deploying the feature
on http://issues.bestpractical.com

Thanks for updating the wiki

-kevin