I'm suffering from timeouts when trying to refresh Jira queries in my Mylyn Task List view. When I snoop the HTTP requests being generated I notice that Mylyn seems to be requesting all issues rather than the ones specified in my query, e.g.
> I'm suffering from timeouts when trying to refresh Jira queries in my
> Mylyn Task List view. When I snoop the HTTP requests being generated I
> notice that Mylyn seems to be requesting all issues rather than the ones
> specified in my query, e.g.
>
> /secure/IssueNavigator.jspa?view=rss&decorator=none& reset=true&tempMax=500&updated:previous=-132584m& ;sorter/field=updated&sorter/order=DESC
That looks like the query that is run to determine the changed tasks. Please
file a new bug report so we can investigate further why this is causing
timeouts.
Also note that a related bug report has been filed here:
> All this worked fine on Mylar and this issue has caused a rather
> embarrassing aborted attempt to roll this out to my team.
I am sorry to hear that. Old version used a slightly different approach for
synchronizing changed tasks. Let's discuss optimization strategies on the
bug report.
> I'm suffering from timeouts when trying to refresh Jira queries in my
> Mylyn Task List view. When I snoop the HTTP requests being generated I
> notice that Mylyn seems to be requesting all issues rather than the ones
> specified in my query, e.g.
>
> /secure/IssueNavigator.jspa?view=rss&decorator=none& reset=true&tempMax=500&updated:previous=-132584m& ;sorter/field=updated&sorter/order=DESC
That looks like the query that is run to determine the changed tasks. Please
file a new bug report so we can investigate further why this is causing
timeouts.
Also note that a related bug report has been filed here:
> All this worked fine on Mylar and this issue has caused a rather
> embarrassing aborted attempt to roll this out to my team.
I am sorry to hear that. Old version used a slightly different approach for
synchronizing changed tasks. Let's discuss optimization strategies on the
bug report.