Adding rights to default lifecycle

Hi,

I would like to add the ability to deny setting a ticket status to
rejected for a group of
privileged users, however I’m not quite sure what would be the best way
to do it.

I’ve read RT essentials and it suggests that the best way forward would
be to add a appropriate *_Local.pm
with the relevant code, however having read the documentation for
v4.0.x this is also possible by
defining a new lifecycle.

If defining a new lifecycle is the best solution, where would I find
the information on how the default lifecycle
is defined?

Many thanks in advance.

Best Regards

Martin Wheldon
Greenhills IT Ltd.

Greenhills IT Ltd. is a limited company registered in England and
Wales.
Company Registration No: 06387214
Registered Offices: 2 Greenhills, Claxton, YORK, North Yorkshire, YO60
7SA

Hi,

To answer part of my own question I see the default life cycle can be
found in RT_Config.pm.
Looks like my best option may be to copy the default over to
RT_SiteConfig.pm and modify it there?

Sorry about some of the noise.

Best Regards

MartinOn 2013-02-09 20:05, Martin Wheldon wrote:

Hi,

I would like to add the ability to deny setting a ticket status to
rejected for a group of
privileged users, however I’m not quite sure what would be the best
way to do it.

I’ve read RT essentials and it suggests that the best way forward
would be to add a appropriate *_Local.pm
with the relevant code, however having read the documentation for
v4.0.x this is also possible by
defining a new lifecycle.

If defining a new lifecycle is the best solution, where would I find
the information on how the default lifecycle
is defined?

Many thanks in advance.

Best Regards


Martin Wheldon
Greenhills IT Ltd.

Greenhills IT Ltd. is a limited company registered in England and
Wales.
Company Registration No: 06387214
Registered Offices: 2 Greenhills, Claxton, YORK, North Yorkshire,
YO60 7SA

Martin Wheldon wrote:

Hi,

To answer part of my own question I see the default life cycle can be
found in RT_Config.pm.
Looks like my best option may be to copy the default over to
RT_SiteConfig.pm and modify it there?

Don’t modifiy it but make a complete copy and use that as a template for
you new lifecyle. After finishing it, restart your webserver/RT and use
the new lifecycle on the queue(s) where needed.

WARNING: if you have tickets in the queue where you’re changing
lifecycles beware that if you don’t have a superset of the original that
there are currently problems with reassigning statussen(?).
This has come up on the list this week so look at the archives to find it.

Regards,

Joop

Hi,

To answer part of my own question I see the default life cycle can be
found in RT_Config.pm.
Looks like my best option may be to copy the default over to
RT_SiteConfig.pm and modify it there?

Yes. You may wish to lock down the ability to reject with a custom
right. Read more about lifecycles here:

http://bestpractical.com/rt/docs/latest/customizing/lifecycles.html
http://bestpractical.com/rt/docs/latest/RT_Config.html#Lifecycles

Hi,

Many thanks everyone for your responces, I’ll give it a go at the
weekend.

Best Regards

MartinOn 2013-02-10 19:28, Thomas Sibley wrote:

On 02/10/2013 12:10 AM, Martin Wheldon wrote:

Hi,

To answer part of my own question I see the default life cycle can
be
found in RT_Config.pm.
Looks like my best option may be to copy the default over to
RT_SiteConfig.pm and modify it there?

Yes. You may wish to lock down the ability to reject with a custom
right. Read more about lifecycles here:

Customizing/Lifecycles - RT 5.0.3 Documentation - Best Practical
RT Config - RT 5.0.3 Documentation - Best Practical