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 165807 - after closing an issue from commit dialog its opened in an unrefreshed state
Summary: after closing an issue from commit dialog its opened in an unrefreshed state
Status: RESOLVED WORKSFORME
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-22 13:07 UTC by Tomas Stupka
Modified: 2011-09-29 15:03 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Stupka 2009-05-22 13:07:03 UTC
originally reported in issue #165656 ...

I did notice another issue that is likely related to this one though.

If I do a COMMIT and FIX/CLOSE a bugzilla issue (that is NOT OPEN in a NetBeans tab), the commit goes CLEAN, and the
BugZilla update goes without error or popup.  -- Then automatically the BugZilla ticket opens in a TAB (nice feature),
but it shows the ticket status from BEFORE the commit.  

EVEN THE refresh button does NOT seem to show the ticket in FIXED-state, with the updates from the commit.
I close the TAB, then go back into FIND_ISSUES, and now the ticket opens with the correct updates & state.

Can you confirm the above? (that a commit results in a STALE ticket being show, that doesn't refresh with the
refresh-button?)

thanks -- MikeE
Comment 1 Tomas Stupka 2009-05-22 13:20:21 UTC
i've tried a couple of times, but unfortunately, i wasn't able to not reproduce. 

does this happen every time you make the action or only that 1 time?
Comment 2 mikee11 2009-05-22 18:07:55 UTC
it appears to happen every time. 

Whats interesting is that the "stale" ticket that comes up (in my case ticket 103) shows an "assigned to" of the
"local/short name". (the "refresh" button doesn't seem to resolve the issue, and the ticket is still stale)

If I close that tab, go to the netbeans issue-search service, and open issue 103, the FRESH ticket comes up (that has
the details in it), but its "assigned to" field has FQDN.....

Are we dealing with some sort of side-effect related to the "local name" fix?
(I have the "local name" checkbox turned on, and have "@yourcompany.com" defined as the "append-to" suffix in the
bugzilla configuration)
Comment 3 mikee11 2009-05-23 06:32:43 UTC
a little more interesting information --

if I go to netbeans/services/find issue and I put in issue 103, it displays the ticket, and in the assigned-to box, it
has an FQDN userid.

if however, I go to a file (that has made reference to that ticket) and do a:  subversion/show_history, it displays a
link to issue 103. If I click on that link, it pulls up the ticket. But the "assigned to" text is in a
GREEN-highlighted/background-box, and the field is NOT FQDN (short-name instead).

This discrepancy is likely at the root of the refresh/stale ticket issue... What is that green background around the
"assigned to" text-field in the 2nd case?

Comment 4 Tomas Stupka 2009-05-25 10:48:34 UTC
> This discrepancy is likely at the root of the refresh/stale ticket issue... 
more like it's caused by the same problem

> What is that green background around the "assigned to" text-field in the 2nd case?
that the fields value has changed since the last you have opened it in the issue window. That's of course technically
seen not true in your case as the short-named or FQDN represent the same value. 
Comment 5 Tomas Pavek 2010-07-23 11:45:35 UTC
Is this issue still valid (still exists)?
Comment 6 Tomas Stupka 2011-09-16 12:07:33 UTC
fixed
http://hg.netbeans.org/core-main/rev/269b357900df
Comment 7 Quality Engineering 2011-09-17 14:16:49 UTC
Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/269b357900df
User: Tomas Stupka <tstupka@netbeans.org>
Log: Issue #165807 - after closing an issue from commit dialog its opened in an unrefreshed state
Comment 8 Tomas Stupka 2011-09-29 15:01:44 UTC
oops, the fix in #269b357900df was mentioned for issue #177581
Comment 9 Tomas Stupka 2011-09-29 15:03:23 UTC
and anyway - no response to last request by tpavek, from reporter for a very long time, so closing as worksforme

feel free to reopen in case you are able to reproduce with a current build