This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 243660 - Refresh task filters doesn't work
Summary: Refresh task filters doesn't work
Status: RESOLVED FIXED
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Jira (show other bugs)
Version: 8.0
Hardware: PC Other
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-08 13:39 UTC by svierkant
Modified: 2014-04-28 09:17 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log (141.40 KB, text/plain)
2014-04-22 15:34 UTC, svierkant
Details

Note You need to log in before you can comment on or make changes to this bug.
Description svierkant 2014-04-08 13:39:14 UTC
When refreshing the task filters in the task pane, only the issues from existing filers are being synced. Refreshing the tasks after removing or adding favorite filters in JIRA has no (direct) effect.

The favorite filters are being synced after NetBeans is restarted, but starts with an error when a new filter is added:

com.atlassian.connector.eclipse.internal.jira.core.service.JiraException: Project with key NEWFILER not found in local cache. Please refresh repository configuration.

It is not clear how to refresh the repository configuration (it isn't Edit Task Repository or Tools/Options/Team/Versioning), but 'Reload Attributes' from 'Find Tasks' did the job.

If you want to refresh all issues from a particular filter, you should use 'refresh' after clicking on a filer. When clicking on the refresh icon on top of the list, the complete list should be refreshed; not just issues from the current view.
Comment 1 svierkant 2014-04-22 15:34:35 UTC
Created attachment 146885 [details]
log
Comment 2 Tomas Stupka 2014-04-25 10:03:12 UTC
'Reload Attributes' stands for refreshing the repository configuration. Maybe we should rephrase the error message ...

> When refreshing the task filters in the task pane, only the issues from existing filers are being synced. 
that's how the action is meant to work. 
> Refreshing the tasks after removing or adding favorite filters in JIRA has no (direct) effect.
do not understand, please elaborate ...
Comment 3 Tomas Stupka 2014-04-25 14:24:08 UTC
fixed in core-main #8e27b5326e38
Comment 4 svierkant 2014-04-25 15:02:46 UTC
If I (un)mark a filter in JIRA as favorite, I doesn't (dis)appear in NetBeans automatically, even after I click on refresh. I have to open 'Find tasks...' to click on 'Reload Attributes'.
Comment 5 Tomas Stupka 2014-04-25 15:45:49 UTC
> If I (un)mark a filter in JIRA as favorite, I doesn't (dis)appear in NetBeans automatically, 
> even after I click on refresh. I have to open 'Find tasks...' to click on 'Reload Attributes'.
the repository configuration is cached on the client as it isn't convenient to download/refresh it on every query refresh (or some other server access). Typically, there is much changes of such kind.

we could investigate if there is a way to find out if the server settings changed since the last download and retrieve the configuration in such a case. Until then, you have to rely on reload attributes (as this is what it is meant for - to refresh the server configuration on the client). 

filled issue #244082 to track this
Comment 6 svierkant 2014-04-25 16:05:38 UTC
Ok, thanks :). Adding a 'reload attributes' button to the Tasks pane would be an option for me as well.
Comment 7 Quality Engineering 2014-04-27 01:21:43 UTC
Integrated into 'main-silver', will be available in build *201404270001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/8e27b5326e38
User: Tomas Stupka <tstupka@netbeans.org>
Log: Issue #243660 - Refresh task filters doesn't work
Comment 8 Tomas Stupka 2014-04-28 09:17:54 UTC
(In reply to svierkant from comment #6)
> Ok, thanks :). Adding a 'reload attributes' button to the Tasks pane would
> be an option for me as well.
added to issue #244082 - let's track the problem there as it is more an enhancement than a bug ...