Eclipse Community Forums: Mylyn » Trac 0.11 + Mylyn: Weird Query results

Help

Home

Home » Eclipse Projects » Mylyn » Trac 0.11 + Mylyn: Weird Query results

Show: Today's Messages :: Show Polls :: Message Navigator

Trac 0.11 + Mylyn: Weird Query results [message #66324]

Tue, 10 March 2009 11:48

Geraint Hywel

Messages: 23
Registered: July 2009

Junior Member

I'm transferring a Trac 0.10 environment to a new server. As part of that
process, I'm upgrading to Trac 0.11 following the instructions at
http://trac.edgewall.org/wiki/TracUpgrade.

I'm seeing some odd results with Mylyn queries based on the Ticket Owner:

Tickets that got carried over from 0.10 environment successfully show up in
the query results.

New Tickets that I create in Trac 0.11 environment do *not* show up, though.

Tickets that *should* match my query appear in the repository's "Unmatched"
container if I

* create a task with Mylyn
* create a task with the email2trac plugin

If I use a browser to create a Ticket that should match my query, it doesn't
show up at all. I can search the repository, and find it that way. If I
add some context (by adding a comment), then it shows up in
the "Uncategorized" container.

Anyone seen anything like this, before?

Some background:

I'm seeing these results on Linux/Eclipse 3.3.2 with Mylyn 3.0.3, and
Windows XP/Eclipse 3.3.2 with Mylyn 3.0.3 (Trac Connector 3.0.5).

I see from http://wiki.eclipse.org/index.php/Mylyn_FAQ#Trac_Connector that I
should be able to get Trac 0.11 talking to Mylyn:

* I don't use a custom work-flow, so the missing functionality shouldn't
affect me.
*Also, I'm logged in as an administrative user, so, at this point, I don't
think I need to worry about the XmlRpcPlugin patch.

I also read this article:
http://nil.checksite.co.uk/post.cfm/trac-0-11-and-mylyn

.... and so I'm using XmlRpcPlugin from trunk.

Report message to a moderator

Re: Trac 0.11 + Mylyn: Weird Query results [message #66440 is a reply to message #66324]

Thu, 12 March 2009 11:38

Geraint Hywel

Messages: 23
Registered: July 2009

Junior Member

Geraint Howell wrote:

> Tickets that *should* match my query appear in the repository's
> "Unmatched" container if I
>
> * create a task with Mylyn
> * create a task with the email2trac plugin
>
> If I use a browser to create a Ticket that should match my query, it
> doesn't
> show up at all. I can search the repository, and find it that way. If I
> add some context (by adding a comment), then it shows up in
> the "Uncategorized" container.

Hmm. I tried upgrading to Mylyn 3.1 on my XP box. Now, no matter which
route I used to create a Ticket, those created since upgrading to Trac 0.11
don't appear at all in Mylyn, unless I manually "Search repository for key
or summary...".

When I open a Ticket that I've searched for, Mylyn tells me that it's "Not
in Task List. Click to add." When I do this, the Ticket appears in
the "Uncategorized" container.

Report message to a moderator

Re: Trac 0.11 + Mylyn: Weird Query results [message #66461 is a reply to message #66324]

Thu, 12 March 2009 16:25

Geraint Hywel

Messages: 23
Registered: July 2009

Junior Member

Geraint Howell wrote:

> I'm seeing some odd results with Mylyn queries based on the Ticket Owner:

After writing my own script to query Trac via XML-RPC, it looks like my
installation of XmlRpcPlugin's ticket.query() method is returning a maximum
of 100 results.

If I exclude closed tickets from my Mylyn query (thereby bring the total
number of results to <100), then I get the results I'd expect.

Strangely, the XmlRpcPlugin on my Trac 0.10 install is *not* limited to 100
results - I don't know why I'm seeing different behaviour, here.

However, the fault doesn't appear to be anything to do with Mylyn. I
thought I'd post that outcome here in the hope of saving someone some
frustration.

G.

Report message to a moderator

Re: Trac 0.11 + Mylyn: Weird Query results [message #66480 is a reply to message #66461]

Thu, 12 March 2009 20:07

Steffen Pingel

Messages: 706
Registered: July 2009

Senior Member

Geraint, thanks for posting the solution to this problem. Here are some
links to related discussion:

http://trac-hacks.org/ticket/3509
http://dev.eclipse.org/newslists/news.eclipse.tools.mylyn/ms g01614.html

I have opened a bug:

268427: query only returns first 100 matches
https://bugs.eclipse.org/bugs/show_bug.cgi?id=268427

Steffen

Geraint Howell wrote:

> Geraint Howell wrote:
>
>> I'm seeing some odd results with Mylyn queries based on the Ticket Owner:
>
> After writing my own script to query Trac via XML-RPC, it looks like my
> installation of XmlRpcPlugin's ticket.query() method is returning a
> maximum of 100 results.
>
> If I exclude closed tickets from my Mylyn query (thereby bring the total
> number of results to <100), then I get the results I'd expect.
>
> Strangely, the XmlRpcPlugin on my Trac 0.10 install is *not* limited to
> 100 results - I don't know why I'm seeing different behaviour, here.
>
> However, the fault doesn't appear to be anything to do with Mylyn. I
> thought I'd post that outcome here in the hope of saving someone some
> frustration.
>
> G.

--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com

Report message to a moderator

Re: Trac 0.11 + Mylyn: Weird Query results [message #66522 is a reply to message #66480]

Fri, 13 March 2009 09:20

Geraint Hywel

Messages: 23
Registered: July 2009

Junior Member

Steffen:

Steffen Pingel wrote:
> Geraint, thanks for posting the solution to this problem.

Actually, the items_per_page config solution mentioned in the links you
provided is probably better:

> Here are some
> links to related discussion:
>
> http://trac-hacks.org/ticket/3509
> http://dev.eclipse.org/newslists/news.eclipse.tools.mylyn/ms g01614.html
>
> I have opened a bug:
>
> 268427: query only returns first 100 matches
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=268427

I think it would be a good idea to have (at least one of) these links on the
wiki at http://wiki.eclipse.org/Mylyn_FAQ#Does_Mylyn_support_Trac_0. 11.3F

Many thanks for your help.

Regards

G.

Report message to a moderator