Hello,
Last week we have installed Request Tracker in our office. When customizing it
I have encountered a problem I was able to solve but there are some issues I
would like to point out.
I created a custom lifecycle in RT_SiteConfig and assigned it to a queue. This
worked without problem.
On Thu, Feb 07, 2013 at 09:31:53AM +, Martin Klíma wrote:
The main issue seems to me that assigning a lifecycle to a queue does
not migrate the tickets in the queue to a new lifecycle. I should
have got There is no mapping for statuses error when I was
assigning the new lifecycle.
This
- Original Message -
From: Kevin Falcone falc...@bestpractical.com
This is a known bug we've been discussing how to fix. There's a lot
of magic that needs to happen when you change a lifecycle midstream.
You have to leave transitions in place until you migrate away from the
old
Many thanks for your reply, Kevin.
Fixing the error message to say something about transitions rather than maps
should be fixable for 4.0, please file a bug about that?
All right, will do
This should not be the case since 4.0.9. What version of RT did you install?
The current release
On Thu, Feb 07, 2013 at 11:06:51AM -0500, Jay Ashworth wrote:
Is there already something in RTs internals for handling queued jobs?
There is not.
If not, is this a big enough issue -- and might you gain useful leverage
in the future -- from introducing it?
Already being discussed. There are
- Original Message -
From: Kevin Falcone falc...@bestpractical.com
On Thu, Feb 07, 2013 at 11:06:51AM -0500, Jay Ashworth wrote:
Is there already something in RTs internals for handling queued
jobs?
There is not.
If not, is this a big enough issue -- and might you gain useful
