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 230770 - not able to see bugzilla issues in nb 7.4.. same thing working 7.3
Summary: not able to see bugzilla issues in nb 7.4.. same thing working 7.3
Status: RESOLVED INCOMPLETE
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 7.4
Hardware: PC Linux
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2013-06-05 09:09 UTC by adithyank
Modified: 2013-06-06 22:08 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
issue view success in 7.3 and not working in 7.4 (170.84 KB, image/png)
2013-06-05 09:12 UTC, adithyank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description adithyank 2013-06-05 09:09:05 UTC
Product Version = NetBeans IDE 7.3 (Build 201302132200)
Operating System = Linux version 2.6.32-358.6.2.el6.i686 running on i386
Java; VM; Vendor = 1.7.0_21
Runtime = Java HotSpot(TM) Client VM 23.21-b01

i am not able to view the bugzilla issues using issue tracker service of nb 7.4 but, same nb bugzilla is accessible from my nb 7.3.
i am having direct internet connection with my laptop and proxy "NO PROXY" set for both the IDE versions.
Comment 1 adithyank 2013-06-05 09:10:09 UTC
attachment created
Comment 2 adithyank 2013-06-05 09:12:48 UTC
Created attachment 135366 [details]
issue view success in 7.3 and not working in 7.4

not able to create attachment through IDE. trying through browser now
Comment 3 Ondrej Vrabec 2013-06-06 06:52:47 UTC
run the IDE with -J-Dorg.netbeans.modules.bugzilla.Bugzilla.level=-1 and -J-Dorg.netbeans.libs.bugtracking.mylyn.level=-1, then attach the messages.log (http://wiki.netbeans.org/FaqLogMessagesFile) when you reproduce the problem and reopen the issue. thanks
Comment 4 adithyank 2013-06-06 22:08:43 UTC
Not able to reproduce it now. It is working now. So, leaving the status as RESOLVED.