Admin: 4 revisions imported

2016-04-06T20:03:36Z

4 revisions imported

← Older revision		Revision as of 16:03, 6 April 2016
(No difference)

75.147.59.54 at 18:21, 12 February 2014

2014-02-12T18:21:57Z

← Older revision		Revision as of 14:21, 12 February 2014
Line 1:		Line 1:
			{{Template:Outdated}}

			Please use [http://bestpractical.com/docs/rt/latest/customizing/lifecycles.html Lifecycles] to accomplish this, on RT 4.0 and higher.

			----


	RT has several built-in status codes, including "new", "open", "resolved", and "stalled".		RT has several built-in status codes, including "new", "open", "resolved", and "stalled".

80.95.70.19 at 11:43, 26 July 2011

2011-07-26T11:43:24Z

New page

RT has several built-in status codes, including "new", "open", "resolved", and "stalled".

Not everyone's work-flow fits nicely into using these particular status codes. One answer is to use custom fields. This has been discussed at length e.g; [http://marc.theaimsgroup.com/?t=108198727400001&r=1&w=2 discussion from 2004]

However, if you "Use custom fields" is unsatisfactory, you can in fact add new statuses to RT. [=etc/[[RT Config|RT_Config]].pm] states:

You can define new statuses and even reorder existing statuses here.
WARNING. DO NOT DELETE ANY OF THE DEFAULT STATUSES. If you do, RT
will break horribly.

The statuses you add '''must be''' no longer than 10 characters: if they are, it will seem to work until you try to actually set one of the long values, at which point you will get an "Invalid status for #nn" error.

Some statuses that have been suggested are:

* '''wcr''' or '''pending''' - Waiting for Customer Response to a question in the ticket
* '''finished''' - a task is Finished, but still waiting for confirmation from the customer

== Adding statuses to SiteConfig ==

Copy the appropriate lines below into [[SiteConfig]] and add replace the example custom statuses wth your own, then restart RT. See also [[NonTransitioningStatus]]

=== 3.8 ===

Set(@ActiveStatus, qw(new open XXX stalled));
Set(@InactiveStatus, qw(resolved XXX rejected deleted SPAM));

=== Pre-3.8 ===

@ActiveStatus = qw(new open XXX stalled);
@InactiveStatus = qw(resolved XXX rejected deleted);

== After 4.0 ==
After 4.0 a new lifecycle management function is introduced, which includes the statuses.

The old configurations are deprecated, at the webserver restart (For example Apache2), you'll get an error, warning you to change this.

More info: [[CustomStatusesInRt4]]

== Scrip actions for custom statuses ==

For the case where you're adding something like 'finished' to inform the requestor that you believe you have finished the required work and you would like confirmation from them that they're happy with it, a possible solution is:

@ActiveStatus = qw(new open stalled finished) unless @ActiveStatus;

% mysql rt3
mysql> INSERT INTO ScripConditions
(Name, Description, ExecModule, Argument, ApplicableTransTypes, Creator, Created, LastUpdatedBy, LastUpdated)
VALUES ('On Finish', 'Whenever a ticket is finished', 'StatusChange', 'finished', 'Status,Set', 1, NOW(), 1, NOW());

This will give you the additional condition "On Finish" which can be used to send an email to requestors saying "Hi, we believe we've finished the task. Could you please check that it's resolved to your satisfaction and let us know by responding to this email. Thanks." without writing a UserDefined Scrip.

A little nasty maybe - but using the 'StatusChange' module's encapsulation of the required behaviour.

CustomStatuses - Revision history

Admin: 4 revisions imported

75.147.59.54 at 18:21, 12 February 2014

80.95.70.19 at 11:43, 26 July 2011