I created custom lifecycles in RT_SiteConfig.pm long time ago (before upgrading to RT5).
Now I’m getting a crash when validating one of my lifecycles via the admin web interface and I’m not able to move specific tickets between with two queues with error message “mapping not found”. But all mappings are there. Double-checked
Now in order to track down the error - I wanted to re-implement the lifecycles from scratch.
If I remove the lifecycle config from RT_SiteConfig.pm it is still configured via Admin Web. Sure I deleted mason objects and restarted webserver. How can this be? Even after restarting the whole server.
I can edit and save lifecyles via web, but I don’t see where those modifications are stored.
If I put back lifecycle config to RT_SiteConfig.pm and do a change there it is not reflected in the admin web. So what?
What happened? Where are Lifecycles stored in RT5? I cannot find anything in the database. And I can’t see changes from webinterface reflected in my filesystem.
Nor do I see where I can fix my issues as it’s not clear to me where to do the changes.
I already thought I was working on another server or the wrong instance, but his is not the case. There is only one instance, only one config section, only one db, …
What is the new / right way to configure custom lifecycles? The latest RT doc still points to adding them to RT_SIteConfig.pm. The Admin interface lifecycles section is not mentioned with a word.
Update: Documentation is ongoing: GitHub
As an RT admin you can go to Admin->Lifecycles to edit and create lifecycles via the
The web interface allows for easy visualization and editing of lifecycles.
But where is it stored what about the local RT_SiteConfig.pm?
I’m really going crazy about this or do I wear tomatoes on my eyes?
Any help appreciated.