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 174341 - No issue trackin integration on commit
Summary: No issue trackin integration on commit
Status: RESOLVED FIXED
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-12 11:05 UTC by ymajoros
Modified: 2010-04-27 14:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (52.40 KB, text/plain)
2009-10-16 13:23 UTC, ymajoros
Details
screenshot (23.54 KB, text/plain)
2009-10-16 13:37 UTC, ymajoros
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ymajoros 2009-10-12 11:05:47 UTC
There isn 't any "update issue" option on my commit dialog, although JIRA integration seems to work fine. 

I can find issues etc. from Netbeans. But, although I set this up for all my colleagues and it's working for them, I
don't have options to comment or resolve issues from netbeans commit message.

We use subversion 1.6.
Comment 1 Tomas Stupka 2009-10-12 11:43:48 UTC
hm, did you try to resize the commit dialog? 

could you, please, in case it shouldn't be caused by your dialog size, 

- provide a screenshot
- run netbeans with the switch -J-Dorg.netbeans.modules.bugtracking.vcshooks.SvnHook.level=100 and attach your
messages.log file

thanks

Comment 2 ymajoros 2009-10-16 13:23:20 UTC
Created attachment 89620 [details]
messages.log
Comment 3 ymajoros 2009-10-16 13:37:04 UTC
Created attachment 89622 [details]
screenshot
Comment 4 Tomas Stupka 2009-10-16 13:42:35 UTC
it looks like at least two modules are missing in your nb install - bugzilla and bugtracking.bridge. 

Bugtracking.bridge is needed for the support in the commit dialog. Could it be you disabled some modules in the plugin
manager? It might be either those two or another one the bugzilla or bridge module are depending on.
Comment 5 ymajoros 2009-10-19 13:22:49 UTC
I'm using JIRA, not Bugzilla. Jira plugins are installed. The missing one was rather "Team" (although I didn't uninstall
it).
Comment 6 Tomas Stupka 2009-10-19 13:45:39 UTC
> I'm using JIRA, not Bugzilla. Jira plugins are installed. 
doesn't matter - it's the missing bugtracking.bridge which seems to be the cause for your problem. And the question is
what happened to the module? Any ideas? did you get any warnings when installing the ide or running it for the first time?

> The missing one was rather "Team" (although I didn't uninstall it).
I guess Team is between the installed modules in your plugin manager. Right? 
Did you deactivate or uninstall any other modules? 
Comment 7 Tomas Stupka 2009-10-19 14:00:24 UTC
>> The missing one was rather "Team" (although I didn't uninstall it).
> I guess Team is between the installed modules in your plugin manager. Right? 
> Did you deactivate or uninstall any other modules? 
i was able to reproduce by e.g. deactivating mercurial (bugtracking.bridge depends on it so was also deactivated) and
then installing the JIRA modules fro UC. The bugtracking modules get activated again, but for the bugtracking.bridge as
JIRA has no declared dependency on it
Comment 8 Tomas Stupka 2009-10-19 15:55:43 UTC
a way to fix your problem would be to:
1.) install the module manager via "Main Menu > Plugins > Available Plugins". 
2.) go to  "Main Menu > Module Manager > Team" and activate the bugtracing.bridge module


Comment 9 Tomas Stupka 2010-04-27 14:38:44 UTC
should be fixed now