Translate custom lifecycle

Hi everybody.

I see the ��standard lifecycle ��has all status translated.

How can I do that with my custom lifecycle ?

Thanks.

Regards.

JAS
Albert SHIH
DIO b�timent 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
T�l�phone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
mer 26 mar 2014 17:03:09 CET

You have to add transitions into RT_SiteConfig from/to each of your states, like this:

Set ( %Lifecycles, test => {
initial => [‘new’],
active => [‘open’, ‘on_hold’, ‘waiting’],
……
transitions => {
new => [ ‘open’, ‘on_hold’, ‘waiting’],
open => [ ‘new’, ‘on_hold’, ‘waiting’],
on_hold => [ ‘new’, ‘waiting’, ‘open’],
waiting => [ ‘new’, ‘open’, ‘on_hold’],
},

...<snip>

-Justin

Le 26/03/2014 � 11:12:10-0700, Justin Killen a �crit

You have to add transitions into RT_SiteConfig from/to each of your states, like this:

Set ( %Lifecycles, test => {
initial => [‘new’],
active => [‘open’, ‘on_hold’, ‘waiting’],
……
transitions => {
new => [ ‘open’, ‘on_hold’, ‘waiting’],
open => [ ‘new’, ‘on_hold’, ‘waiting’],
on_hold => [ ‘new’, ‘waiting’, ‘open’],
waiting => [ ‘new’, ‘open’, ‘on_hold’],
},

Sorry…my question isn’t very clear…

new/open/on_hold is in english when I choose english in the interface. But
it’s in french/german/etc. when I choose french/german/etc. in the interface.

How can I do the same for my own Lifecycle ?

Regards.

JAS
Albert SHIH
DIO b�timent 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
T�l�phone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
mer 26 mar 2014 19:32:41 CET

new/open/on_hold is in english when I choose english in the interface. But
it’s in french/german/etc. when I choose french/german/etc. in the interface.

How can I do the same for my own Lifecycle ?

You’ll want to look at the po files that ship with RT, which contain
translations. If you had a local/po/fr.po with

msgid "New Status"
msgstr “Statut Nouveau”

RT would translate statuses.

There’s more infrastructure needed to tag and extract automatically
(which is what we’re doing) but for a fixed and known lifecycle, you
could just manually create .po files.

-kevin