Geertjan's Blog

  • August 14, 2013

New Task Management in NetBeans IDE 7.4

Geertjan Wielenga
Product Manager

Especially handy for enterprises with large bugtracking databases, NetBeans IDE 7.4, currently in its Beta release, introduces a new Task Management Window. The details are described here:


Prior to NetBeans IDE 7.4, though there was support for registering bug trackers, the overview of queries was poor, there were no access points for task management in general, and no categories. In contrast, below you can see that the results of my queries are displayed in a list, i.e., in the Task Management Window, from where I can categorize them:

I know I'll be fixing my issues much faster than before, now that they're integrated directly into my development environment. No excuse to avoid them now... 

Both Bugzilla and JIRA are supported out of the box. The Options window lets you configure the above window, e.g., how often the list should be automatically refreshed.

Also note that this is seen as part of a continuing process of enhancing the support for task management in NetBeans IDE. Features for scheduling tasks could be added in future releases, for example, as well as the co-ordination of tasks with other features of the IDE.

Join the discussion

Comments ( 7 )
  • Sean Phillips Wednesday, August 14, 2013

    The Task Management support has always been interesting to me. I'd love to roll it out on my NetBeans Platform apps so software operators can associate Day-In-The-Life operations with our Ticketing system. This could be a very powerful way for any instance within an Enterprise workflow to be tracked from cradle to grave whether it is a Factory lot or Data products produced on my NASA mission.

    Unfortunately for me we use Trac which is no longer supported officially.

    The original writers of this software had some limited but functional support for Trac when the plugin was called Cubeon and I did manage to get that plugin to work in older versions of NetBeans. I suppose it is possible that Trac support could be resurrected.

  • guest Wednesday, August 14, 2013

    I agree, the direction is correct and nice.

    But netbeans has a serious flaw in this functionality: There is no stable SPI. So external developers suffer from breaks each time someone decides to bump the implementation version of the issue tracker module. There are three P1 bugzilla entries each refering to missing integration of one bugtracker and a P1 requesting a stable API (162279, 164174, 168018, 175564).

    Only the netbeans core team can provide bugtracker integration easily, because they can ignore the fact, that only a friend SPI is in place.

  • Konstantin Bulenkov Friday, August 16, 2013

    Nice! I'd recommend to make filters (Major, Critical, Fixed, etc) and read/unread flags. I made this http://www.screenr.com/8i8H in two days during JetBrains Hackathon. The main idea is that issue tracker should be like an e-mail client.

    Wish you good luck!

  • guest Saturday, August 17, 2013

    It would be really cool to introduce something like Pomodoros that can be accessible either through your ide, a table, smartphone etc. For me JIRA (an issue tracker) lacks components to handle interruptions in the day. The regular pomodoro model lacks the always accessible part. However, that is partly by design as you really need to put work aside once in a while.

    see http://www.pomodorotechnique.com/ for more

  • Mike Colegrove Saturday, August 17, 2013

    It would be really cool to integrate something like the Pomodoro technique that allows you to set a plan 25 minute chunks each task. It also has a feature to handle unforseen interuptions. Jira and many other issue trackers do not seem to address managing multiple tasks that way. See http://www.pomodorotechnique.com/ for some details.

  • Mike Levine Sunday, August 18, 2013

    I second the comment regarding the stability of the issue tracking SPI, which severely limits the ability for 3rd party tools to provide support for any other issue tracking platforms.

    As was previously mentioned by guest on August 14, this has been a very longstanding issue --- on the order of 3 years already. Honestly, it is unconscionable that such a serious limitation should be allowed to continue in the software for so long.

    No one is asking the NetBeans dev team to provide support for the multitude of other platforms outside of Jira and Bugzilla. The issue here is that there are *MANY* people who require this support and *MANY* developers who are willing to provide plugins to provide this support, but are impeded by this unresolved issue.

    Incidentally, I did a quick review of the online javadocs for the current and development versions and I did not see anything there related to Issue Tracking. Even if the reason that the SPI is presently unstable is that you are still tweaking things and trying to figure out the best way to implement this subsystem, at least publish as much as you presently have. That way, we will be able to use it in the interim, and perhaps community feedback will be most helpful in assisting you to settle on a final, stable API.

    Can you please explain what is the underlying difficulty here, and why these bugs have remained open for over 3 years?

    Thanks and all the best

  • Geertjan Sunday, August 18, 2013
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.