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 247291 - Cannot connect to on-premise or Atlassian-hosted Jira with lates JIRA plugin version 1.52
Summary: Cannot connect to on-premise or Atlassian-hosted Jira with lates JIRA plugin ...
Status: RESOLVED FIXED
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Jira (show other bugs)
Version: 8.0.1
Hardware: PC Windows 7
: P1 normal with 4 votes (vote)
Assignee: Tomas Stupka
URL:
Keywords:
: 247178 249341 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-09-19 08:44 UTC by heapifyman
Modified: 2016-06-01 16:35 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (112.09 KB, text/plain)
2014-09-19 08:45 UTC, heapifyman 		Details
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 heapifyman 2014-09-19 08:44:59 UTC 
Updated to latest version of JIRA plugin (1.52)
Connector type is set to version 5.0+

Loading issues in the Tasks view does not succeed for both:
- an Atlassian-hosted Jira v6.4-OD-05-008
- and an on-premise Jira v6.3.4

The connection settings dialog just keeps re-appearing for both JIRA connections until I click "cancel".
It is not an issue with the credentials because
a) clicking Validate in the connection setting dialog yields a "connection successful" and 
b) I can login to both web-frontends with the same credentials

Also, when changing connector type to Jira 3.13+ connection is established and task are successfully retrieved for both Jira instances



Product Version = NetBeans IDE 8.0.1 (Build 201408251540)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0_20
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.20-b23
Comment 1 heapifyman 2014-09-19 08:45:05 UTC 
Created attachment 149357 [details]
IDE log
Comment 2 koshua 2014-09-22 10:28:16 UTC 
Have the same issue, deleting the JIRA repository and creating a new one solves the problem temporary...
Comment 3 heapifyman 2014-09-24 15:34:42 UTC 
Tried deleting and re-creating the JIRA repository. No change.
Connection is still refused.
Comment 4 HWeber 2014-09-26 06:19:29 UTC 
I have the same issue, deleting the Jira repository and reinstalling netbeans didn't help.
Comment 5 rubenflush 2014-10-01 12:39:58 UTC 
Same issue here... Why is this plugin even certified?
Comment 6 svierkant 2014-10-13 13:06:55 UTC 
Same issue here.

*** This bug has been marked as a duplicate of bug 247278 ***
Comment 7 heapifyman 2014-10-15 15:59:08 UTC 
Still does not work with Jira plugin version: 1.52.1
Comment 8 HWeber 2014-10-16 07:21:50 UTC 
Same here with version 1.52.1.
I retried it several times. It seems that the plugin tries to connect with the wrong password, because after that I can only login with my password and a CAPTCHA. Normally this only appears if I tried to login several times with a wrong password.
Comment 9 urfin 2014-10-16 08:32:42 UTC 
Same here with 1.52.1
Comment 10 rubenflush 2014-10-16 09:17:12 UTC 
Temporary fix is to enter a different repository name. Then it logs you in (works for me)
Comment 11 heapifyman 2014-10-16 10:27:40 UTC 
(In reply to rubenflush from comment #10)
> Temporary fix is to enter a different repository name. Then it logs you in
> (works for me)

That seems to work. Thanks.
But why is this not mentioned in the plugin release notes / changelog??
Comment 12 Tomas Stupka 2014-10-17 17:13:11 UTC 
*** Bug 247178 has been marked as a duplicate of this bug. ***
Comment 13 Tomas Stupka 2014-10-17 17:21:36 UTC 
will try to reproduce on a jira version as reported

and also add some more logging - in the meantime, if somebody is also able to reproduce with a dev build, please wait until it is announced in this issue that it was integrated into the daily builds, run NB with the cli switch 
-J-Dorg.netbeans.modules.bugtracking.logPasswords=true

try to reproduce and check if your credentials were correctly logged just before the exception appears

thanks
Comment 14 Tomas Stupka 2014-10-24 12:45:11 UTC 
added logging is part of daily builds now
Comment 15 Quality Engineering 2014-10-29 11:43:25 UTC 
Integrated into 'main-silver', will be available in build *201410290913* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/977e9edafdc6
User: Tomas Stupka <tstupka@netbeans.org>
Log: more logging

issue #247291 - Cannot connect to on-premise or Atlassian-hosted Jira with lates JIRA plugin version 1.52
Comment 16 rustedwolf 2014-10-31 07:31:59 UTC 
(In reply to rubenflush from comment #10)
> Temporary fix is to enter a different repository name. Then it logs you in
> (works for me)

That worked for me. Strange workaround...
Comment 17 Tomas Stupka 2015-01-23 16:30:36 UTC 
*** Bug 249341 has been marked as a duplicate of this bug. ***
Comment 18 Tomas Stupka 2015-01-23 16:32:00 UTC 
fixed in jet-main #8a1108a40091
Comment 19 Quality Engineering 2015-01-24 02:35:21 UTC 
Integrated into 'main-silver', will be available in build *201501240002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/8a1108a40091
User: Tomas Stupka <tstupka@netbeans.org>
Log: Issue #247291 - Cannot connect to on-premise or Atlassian-hosted Jira with lates JIRA plugin version 1.52
Comment 20 Tomas Pavek 2016-06-01 16:35:06 UTC 
Fix adjusted to be for JIRA only: http://hg.netbeans.org/jet-main/rev/7f657d82f2b3