[rt-devel] Incorrect setting of Time Resolved with multiple inactive states?

[Ruslan Zakirov]

On Wed, Apr 3, 2013 at 11:20 PM, Kevin Falcone <falcone at bestpractical.com>wrote:

> On Wed, Apr 03, 2013 at 10:31:58AM +0200, Davide Imbeni wrote:
> > I have a question / request regarding the setting of Resolved Time for a
> Ticket that changes status.
> > I read in the docs that:
> >
> > RT will automatically set the Resolved date when a ticket's status is
> changed from an Initial or Active status to an Inactive status.
> >
> > What I observed is instead that RT automatically set the Resolved date
> when a ticket's status is changed to an Inactive status, regardless of the
> original status.
> >
> > This might seem a small distinction, but with my Lifecycle it makes an
> important difference.
>
> This dates from the time when for most RTs, you really only had 2
> inactive statuses (yes you could add more, but most people didn't).
> You were rejecting or resolving a ticket and rarely cared about
> toggling between them.
>

Don't know if I introduced regression or just followed old behaviour when
was imlementing lifecycles, but in any case I think this change should be
in RT 4.2.

-- 
Best regards, Ruslan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-devel/attachments/20130404/df0089ff/attachment.html>