[rt-devel] updating RTx::Tags for RT4

[Ruslan Zakirov]

On Thu, May 9, 2013 at 6:58 PM, Darin Perusich <darin at darins.net> wrote:

> Hello All,
>
> I'm attempting to update the RTx::Tags extension,
> http://search.cpan.org/dist/RTx-Tags, to support RT4 since the
> maintainer's no longer using RT and I think it'll be a useful plugin.
> This is my first crack at something like this so bare with me.
>
> In a post about this extension from last year a comment was made that
> it's " building the status list in the old 3.8 way rather than using
> the RT::Queue->ActiveStatusArray". What exactly does this mean?
>

This means that ActiveStatusArray method [1] of RT::Queue object should be
used to get list of statuses in a queue.

If you need all possible active statuses then you should use methods in
RT::Lifecycle module [2].

[1] http://bestpractical.com/rt/docs/latest/RT/Queue.html#ActiveStatusArray
[2] http://bestpractical.com/rt/docs/latest/RT/Lifecycle.html#List


> The extension is also building a select to query the database, see
> http://cpansearch.perl.org/src/JPIERCE/RTx-Tags-0.25/lib/RTx/Tags.pm.
> Is this the best way to do this or should one of the RT::Search
> modules be employed?
>

AFAICS this code will work with 4.0 without problems. You should
concentrate on UI first as most probably to port extension over 4.0 you
just need to change how it puts links into menus.


>
> http://lists.bestpractical.com/pipermail/rt-users/2012-March/075452.html
> https://rt.cpan.org/Public/Bug/Display.html?id=75647
>
> In the mentioned query you have the following part:

*"Tickets.Status IN()"*

Above is not valid SQL. However, it's obvious that empty "IN" list means
that extension just is not able to get list of statuses.


> Thanks!
> --
> Later,
> Darin
>
>
> --
> RT Training in Seattle, June 19-20: http://bestpractical.com/training
>



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