Difference between revisions of "CustomStatusesInRt4"
Jump to navigation
Jump to search
m (9 revisions imported) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'' To see how custom statuses are handled in prior versions refer to this article: [[CustomStatuses]] '' | ''To see how custom statuses are handled in prior versions refer to this article: [[CustomStatuses]] '' | ||
Statuses are based on Lifecycles in RT 4. | Statuses are based on Lifecycles in RT 4. Lifecycles define how your tickets can move into and out of statuses. | ||
For more about Lifecycles, please read the following official documentation: | For more about Lifecycles, please read the following official documentation: | ||
| Line 14: | Line 14: | ||
* If you don't define the transitions part, you won't be able to chose your new statuses in the ticket's basic field: status. | * If you don't define the transitions part, you won't be able to chose your new statuses in the ticket's basic field: status. | ||
Latest revision as of 16:03, 6 April 2016
To see how custom statuses are handled in prior versions refer to this article: CustomStatuses
Statuses are based on Lifecycles in RT 4. Lifecycles define how your tickets can move into and out of statuses.
For more about Lifecycles, please read the following official documentation:
Community contributed hints
(here you can add your hints, tips or anything you thing helpfull)
- At lifecycle from->to you may notice the
'(single quotes) around ABC-E at the from part as'ABC-E'. Unless you do this the-breaks the code
- If you don't define the transitions part, you won't be able to chose your new statuses in the ticket's basic field: status.