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 197407 - JIRA custom fields get repeated values when pushed from NB
Summary: JIRA custom fields get repeated values when pushed from NB
Status: RESOLVED WORKSFORME
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Jira (show other bugs)
Version: 6.x
Hardware: Macintosh (x86) Mac OS X
: P2 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 17:27 UTC by shafquatmahmud
Modified: 2011-09-06 07:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot displaying the issue reported (222.80 KB, image/png)
2011-04-04 17:27 UTC, shafquatmahmud
Details
message log (76.29 KB, application/octet-stream)
2011-04-05 17:56 UTC, shafquatmahmud
Details
Jira custom field configuration screen (138.89 KB, image/png)
2011-04-07 17:05 UTC, shafquatmahmud
Details
All custom fields (214.03 KB, image/png)
2011-04-07 17:09 UTC, shafquatmahmud
Details

Note You need to log in before you can comment on or make changes to this bug.
Description shafquatmahmud 2011-04-04 17:27:43 UTC
Created attachment 107482 [details]
Screenshot displaying the issue reported

Steps:
 - Create some Custom Fields in JIRA (try multi-checkbox and configure some options)
 - Open the issue in Netbeans
 - Add a comment and UPDATE
 - Check the issue in JIRA
Results:
   - values for custom fields are rendered multiple times
   - email fields are rendered incorrectly. check assignee or some other field that takes an email.
Comment 1 Tomas Stupka 2011-04-05 09:22:26 UTC
unfortunately, i wasn't able to reproduce. some more information would be
needed.

what is your jira server version?

please also start netbeans with the switch
-J-Dorg.netbeans.modules.jira.Jira.level=-1, reproduce the problem and attach
then your messages.log 

thanks
Comment 2 shafquatmahmud 2011-04-05 17:56:18 UTC
Created attachment 107520 [details]
message log
Comment 3 shafquatmahmud 2011-04-05 17:58:37 UTC
attached message log.
The previous results were against Jira 4.0. 
Ran against Jira 4.3. Since the Issue summary view doesnt show email for Assignee, the rendering issue of email is not present anymore. However the issue with multiple entries of custom fields exist. The number keeps increasing every time I make a change (change status, priority, close, reopen) to the issue from Plexina.
Comment 4 Tomas Stupka 2011-04-07 16:00:14 UTC
hm, tried jira 3.13, 4.1 and 4.2.2 and still unable to reproduce. seems to be somehow related to your setup...

just a blind try, but what you could do would be to remove the folders:
{userdir}/var/bugtracking
{userdir}/var/cache/bugtracking
Comment 5 Tomas Stupka 2011-04-07 16:01:07 UTC
priority to p2 as this doesn't seem to be a general problem
Comment 6 Tomas Stupka 2011-04-07 16:13:29 UTC
few more things:
- what other kinds of custom fields (that multicheckbox) do you have configured? might be the problem is triggered by some other field type. we could give it a try.

- maybe some other configurations on the server that could be interesting?

- we officially support jira <= 4.1, see also issue #194481. please note that custom fields (just for https://studio.plugins.atlassian.com/wiki/display/LBL/JIRA+Labels+Plugin) aren't handled and touched in the nb jira plugin and the problem might be caused be the third party connector library we use. The planned upgrade could eventually help.
Comment 7 Marian Mirilovic 2011-04-07 16:32:38 UTC
Ok, so waiving this bug for NB 7.0 and leave it as P2 , so we plan to do further analyses and we trust reporter and understand it's critical for him. We will also consider to fix it (if we will be able to do so) in next update release - 7.0.1. Thanks for understanding.
Comment 8 shafquatmahmud 2011-04-07 17:05:54 UTC
Created attachment 107590 [details]
Jira custom field configuration screen

I am surprised to know you could not reproduce it. We tried it on 3 separate installs of Jira 4.0. The email fields are rendered incorrectly on 4.0. For example, this is what I see after every push to Jira issue from NB 6.9.1 : 	<a href='mailto:<a href='mailto:<a href='mailto:<a href='mailto:<a href='mailto:shaf@example.com'>shaf@example.com</a>'><a href='mailto:shaf@example.com'>shaf@example.com</a></a>'><a href='mailto:<a href='mailto:shaf@example.com'>shaf@example.com</a>'><a href='mailto:shaf@example.com'>shaf@example.com</a></a></a>'><a href='mailto:<a href='mailto:<a href='mailto:shaf@example.com'>

Also ran against Jira 4.3. The custom field 'Impact' (as shown in the attached pic) gets repeated value every time the issue is updated by Nb 6.9.1. For example, if 2 fields (mandatory and cost optimization) are selected, every time I update the issue status (or close/reopen the issue) NB sends repeated values to Jira and the 'Impact' field in the issue is displayed as "Mandatory, cost optimization, Mandatory, cost optimization, ......."

I can email you screen shots of every step if you still can't reproduce it. Let me know if you decide not to address it anytime soon - we will have to write our own plugin then as our clients are dependent on this.
Comment 9 shafquatmahmud 2011-04-07 17:09:28 UTC
Created attachment 107591 [details]
All custom fields

These are all the custom fields we have, if this helps. Thanks.
Comment 10 Tomas Stupka 2011-04-11 14:50:44 UTC
tried one more time with 6.9.1 (previosly with a current dev build) but still not able to reproduce. tried even with an issue with all custom field types you have setup.  

> I can email you screen shots of every step if you still can't reproduce it. 
maybe an exact step by step description what you do in the nb client would be enough

did you try after removing the {userdir}/var/ folders (or with an empty userdir) as mentioned in my previous post?

> Let me know if you decide not to address it anytime soon - we will have to write
> our own plugin then as our clients are dependent on this.
we have to try to reproduce first... we could try to upgrade the jira libraries, but that won't happen for 7.0.1
Comment 11 Tomas Stupka 2011-09-06 07:46:22 UTC
jira libraries upgraded in #194481, and still unable to reproduce - so closing as worksforme for now.
feel free to reopen in case the problem should remain.