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 175175 - update issue removes Fix Version content
Summary: update issue removes Fix Version content
Status: RESOLVED DUPLICATE of bug 164916
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Jira (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-22 07:29 UTC by hlang
Modified: 2009-11-24 03:41 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hlang 2009-10-22 07:29:08 UTC 
I use netbeans 6.7 (linux) and JIRA 3.13.4.
When i commit a change to subversion and choose "Update issue" and mark "Resolve as FIXED", the JIRA-plugin changes the
related issue Status in JIRA.

The problem is: a "Fix Version" that was already set for that issue gets removed.

Our way of working is:
- create a issue  (JIRA Web-GUI)
- assign the "Fix Version" (JIRA Web-GUI)
- make the fix and commit to subversion, mark issue fixed (netbeans)
But we loose the "Fix Version" on the last step.
Comment 1 Ondrej Vrabec 2009-10-22 08:48:39 UTC 
Does it happen even when you click on Reload attributes before committing the fix and closing the issue from netbeans.
The 'Reload attributes' button is placed in Team > Find issues in the right lower corner.

Jira plugin caches server configuration - the list of available versions, components, etc. And if e.g. a new version is
created on the server, you will need to refresh the cache in netbeans to let it know about it (with the Reload
attributes button).

So, is it possible that the new version has been created lately and has not been visible in netbeans yet? Or does it
happen every time even after you reload the attributes?
Comment 2 hlang 2009-10-22 10:22:31 UTC 
The problem does not happen if "reload attributes" was used.

If was not aware of "reload attribute" because i did not use netbeans, for browsing the JIRA-issues.
So i checked this: i saw before i reloaded the attribute that the version the issue was assigned as "fixVersion" was not
available in the netbeans view of that issue. After "reload attributes" that version was visible.
Comment 3 Ondrej Vrabec 2009-10-22 11:04:44 UTC 
There may be two possible ways how to deal with this:
1) After IDE starts we could refresh the cached configuration in background
2) Or somehow patch the mylyn connector to better handle this situation - it knows that downloaded issue has a version
which is not currently cached, but decides to ignore it.
Comment 4 Tomas Stupka 2009-11-24 03:41:43 UTC 
vote for 1.) this shouldn't be a typical use case and a silent refresh on start should be enough.

duplicate see issue #164916

*** This bug has been marked as a duplicate of bug 164916 ***