As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
JIRA is a very extensible bug/task tracking tool. As such, newcomers feel lost as to what plugins they should install.
Please share your thoughts what plugins (both free and paid) that you consider a "must-add" for JIRA!
Here are the plugins I couldn't live without:
Timesheet report - Summarizes any user's time spent over a weekly period: http://confluence.atlassian.com/display/JIRAEXT/Timesheet+report+and+portlet
Charting plugin - Generate charts from any issue navigator: http://confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin
Subversion plugin - Link and view subversion commit history to a JIRA issue: http://confluence.atlassian.com/display/JIRAEXT/JIRA+Subversion+plugin
Labels plugin - Lets you tag any JIRA issue and search on tags: http://confluence.atlassian.com/display/JIRAEXT/JIRA+Labels+Plugin
We use JIRA Labels plug-in, which allows to add a "tags" field: http://confluence.atlassian.com/display/JIRAEXT/JIRA+Labels+Plugin
Plugins that stand out the most (paid and free) are mentioned on Atlassian's plugin page:
https://plugins.atlassian.com/search/by/jira
And the company I work for develops JIRA Client, a desktop client for JIRA (paid unless you're open-source): http://almworks.com/jiraclient
We use Tempo Plugin extensively for time tracking, project management, planning and billing.
We are also big fans of Greenhopper for project management (Scrum/KanBan).
We use quite a few extra JIRA plugins; the charts for visualizing find/fix ratios etc., Release status plugin for a nice visualization of how each release stands, the SVN integration, Linker and Activity Stream plugins for integration with Confluence, and the Firefox search portlet that lets you use JIRA as a search engine option in Firefox.
Some of our developers also like the Eclipse plugin for JIRA that lets them manage their list of issues direct from the IDE.
The only paid plugin we tried out was Greenhopper, since we are an agile shop, but we didn't find it useful enough to be worth buying.
We really liked the following:
Create and Link: Allows us to create an issue, then create another issue that automatically gets linked to the original
JIRA Suite Utilities: Incredibly useful plug-in! The most helpful feature was it's ability to make field's required after a transition.
JIRA Misc Workflow Extensions: multiple useful conditions and validators for work flows.
To integrate Jira with Saleforce or SugarCRM you should consider Go2group CRM plugin
We use ScreenMail for JIRA as it lets us create screencasts to our issues. It removes the need to write long descriptions of specifications or bugs. Screencasts makes it possible for me to record my screen and talk whats on my mind to my mic. Anyone who has access to the issues can watch the video later.
This has given me more freedom to work whenever as I do not need to call a meeting always when something more complicated has come up. Work with overseas partners has also been easier as I am able to work in my own timezone most of the time.
Whats important here is that you do not need to install any additional software or rent harddrive space. The plugin does everything for you. Just install the plugin and start recording.
I found the JIRA Workflow Visualization Plugin very useful when first setting up Jira workflows - it gives a pictorial representation of your workflows, which makes it easier to view than the list of steps that Jira gives you by default.
For customizing the way Jira works and adding new features:
Behaviours Plugin
Jira Scripting Suite
With this to you could practically do almost anything. I used it to write Issues 24hrs notifications, sending email from templates that are saved in Confluence, automatic issue moving, closing, cloning and sub-issue creating, and much more...
To complete the last two plugins, some plugins that add special features to make life easier:
JIRA Toolkit Plugin
JIRA Workflow Toolbox
A nice plugin to display external pages:
Jira Custom Content Plugin
For more advanced JIRA reports, charts and dashboards there is eazyBI application with standard JIRA integration as well as installable eazyBI reports and charts plugin for JIRA.
Related
Where can I find a developer guide to kibana, that explain me how the system work and all the things i need to know for developing kibana plugin?
Or if someone could publish snippets of sample plugin.
I've started cloning statusPage plugin, but I don't want to do revers engineering to understand the platform.
On the website, the is no type of developer manual.
Thank you
You can refer to the following links to learn How to develop Kibana Plugins:-
http://logz.io/blog/kibana-visualizations/
https://www.timroes.de/2015/12/02/writing-kibana-4-plugins-basics/
The official answer from 6+ months ago seems to be "don't":
We're working to develop an external API but would caution you away
from making custom changes as things still move pretty fast and
internal APIs are likely to change even in patch versions.
Also, "there are no public plugin APIs right now" (8/2015)
Hard to find any information to date. I recommend you to look at the plugin generator released some days ago:
Generator Kibana Plugin Structure
There are two plugins I found where you can have a look at the code to understand the structure. The first is the Sense plugin, the second Timelion. Timelion matches more to the structure of the generator.
Sense Github
Timelion GitHub
I suggest understanding plugin structure and code for traffic plugin (https://github.com/sbeyn/kibana-plugin-traffic-sg) which would be one of the simplest plugins to understand and you could directly add it to your installed plugin folder in kibana and see it working.
Other than that I would also suggest you do read timroes blogs (https://www.timroes.de/2015/12/02/writing-kibana-4-plugins-basics/) for developing kibana plugins
and last I would also suggest using elasticsearch discussion forum for kibana related issues as well for quicker responses:
https://discuss.elastic.co
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I search a code coverage plugin for eclipse.
My question is simple:
Which plugin do you use with eclipse for code coverage and why ?
Edit (2015) - My current recommendation: EclEmma / JaCoCo.
Not sure why I didn't see this back in January 2012, as there was clearly active development with new versions consistently being reproduced even back then.
I've since become a bit frustrated with Cobertura / eCobertura, as development since seems to have stalled, with support for current Java versions starting to be somewhat lacking.
JaCoCo may have advanced since I last looked at this in 2012 (or I simply missed it entirely, or was looking at EMMA vs. JaCoCo) - but the current version provides excellent support built-in to Eclipse (provided by EclEmma) as well as many other IDEs, support for Apache Maven, Apache Ant, command-line, Java API, and many other third-party integrations. Please refer to the complete list at http://www.eclemma.org/jacoco/trunk/doc/integrations.html .
I am now switching some of my projects over to JaCoCo from Cobertura, and am very impressed by the integration and results - both in Maven reports as well as Eclipse. Not sure about competing solutions, but JaCoCo can even be configured to fail a build if certain thresholds of code coverage are not met.
JaCoCo is specifically documented to support Java class files from version 1.0 all the way through 1.8*.
I find their Mission Statement very respect-worthy.
References / Resources:
Especially as this question has unfortunately been closed, here is a mini-directory of some of the various references and resources that I used in making my decision - and which I encourage everyone here to refer to in order to make their own decisions.
https://en.wikipedia.org/wiki/Java_Code_Coverage_Tools - by Wikipedia's nature is more of a "living document", and will hopefully remain updated with any new related tools that may become available.
The following should also somewhat fall into the same category of a "living document", but fall under probable bias / conflicts of interest - as each is from the vendor or organization that also produces such a tool:
http://www.eclemma.org/resources.html (Provides EclEmma, JaCoCo)
https://confluence.atlassian.com/display/CLOVER/Comparison+of+code+coverage+tools (Provides Atlassian Clover)
Presumably independent but dated reviews and comparisons:
Code Coverage Tools (JaCoCo, Cobertura, Emma) Comparison in Sonar (2012-12-19, Patroklos Papapetrou, onlysoftware.wordpress.com)
Eclipse plugin for code coverage (2012-01-28, stackoverflow.com)
Test coverage: jaCoCo vs Clover2 (Jakub Kurlenda, 2010-12-28, kurlenda.blogspot.com)
Java Code Coverage: Cobertura vs. Emma vs Clover (Tom Borthwick, 2010-10-23, copperykeenclaws.com)
Pick your code coverage tool in Sonar 2.2 (2010-08-05, Evgeny Mandrikov, sonarqube.org)
In pursuit of code quality: Don't be fooled by the coverage report (Andrew Glover, 2006-01-31, ibm.com)
Previous:
eCobertura.
It does the job, it is free and open-source, it is more up-to-date than EMMA, and it is used by most of the other online open-source projects I'm familiar with. It also integrates very well into Maven - including some rather nice-looking reports.
If you want to consider a commercial product, I'd consider Atlassian's Clover.
I like http://codecover.org/
The source highlighting is better than eCobertura, the drill-down is easy to read, selecting test cases is easy, it actually provides statistics for statement, branch, loop and condition coverage ( a lot of plugins only do statement, which is kinda useless ).
We use it at our business and we found it the best plugin by far.
Coverlipse: http://coverlipse.sourceforge.net/ because it's free
is there a way to create a task/activity report (say a weekly report) off tasks managed with Mylyn? I've been using Rachota TimeTracker which allows me to create reports (in html format)
http://rachota.sourceforge.net/en/demo.html
I've just started using mylyn (our company uses Embarcadero JBuilder which is is based on Eclipse), but I don't see anywhere in the Eclipse or Embarcadero docs about reporting capabilities.
Is it possible? Is it possible to query activities worked on a prior week and report statistics out of it (management like reports, you know;) I'm sure it is, but I haven't been able to google it out.
Thanks.
You're in luck, Tasktop Pro (the supported version of Mylyn) has reporting. It allows you to:
View all task activity times for the previous day, week, and month
Manually adjust times as necessary to account for meetings and discussions
Submit your adjusted times, on tasks you select, to your task repository
Create reports in various formats
I'd recommend this short video which explains the reporting features in about 6 minutes.
David Shepherd
Tasktop Technologies
As you already know by now, the reporting functionality is included into commercial Tasktop product, which is developed by the same people who created Mylyn. So, obviously they are not interested to include some features into a free version. Now you have two options, either buy Tasktop, or develop your own extension for Mylyn. The task data is stored in reasonable simple xml file, so you not necessarily have to create an Eclipse plugin.
the reporting feature was stripped from the project when it used to be called mylar, in 2007, and since the project went commercial never came back to the open source mylyn for obvious reasons..
I found this simple perl script which outputs a pretty basic text only report, good enough for me.
http://rachaelandtom.info/mylyn-report
No takers? Not surprised since I can't find anything on the subject. For what's worth, there is an experimental task/activity report available for Mylyn with the sandbox jar. However, I could not get mine to work as I'm tied up with a JBuilder installation behind a firewall (and I can't download anything on the corp network that is not pre-evaluated... it sucks, I know.)
I'm going to have to experiment with the mylyn sandox at home, but it would be great if someone knows of an easier, more stable alternative.
Our small team of 3-4 developers uses a wiki for documentation and collaboration. I'm trying to put together a list of some solid extensions which would help make it better. We are using MediaWiki, but if you know of a good extension/plug-in for another platform I'd like to hear about that too. Thanks.
Here is my list so far:
Geshi for syntax highlighting.
FCKeditor
TagAsCategory
Promising Extensions that don't work w/ MediaWiki 1.15.0
CategoryEditor
IssueTracker
Two things come to mind:
Bug tracking tool integration
SCM tool integration
For MediaWiki there are already
Bugzilla integration:
http://www.mediawiki.org/wiki/Extension:BugzillaReports
SVN integration:
http://www.mediawiki.org/wiki/Extension:SVNIntegration
The whole list of extensions is here
Well, I think that a good starting point would be to check what we use at mediawiki.org, because this is a Development Wiki :)
My first choice would be CodeReview of course. It's not pretty, but it's very useful. See how we use it: it allows to integrate a SVN into the wiki, to add comments on code, tag commits, and put statuses on it.
At MediaWiki, we use new/verified/ok chain, adding fixme/reverted/resolved/deferred when things go wrong; but you're free to use your own statuses here.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
In particular, I need a more full fledged version of Trac to support robust project management, and task tracking. I went through the plugins and literally found over 50 that looked promising.
My question is to the admins/users of Trac: which ones are indespensible for making Trac feature complete and which ones should be avoided (e.g. stability issues)?
Lots of Trac plugins look promising. Unfortunately only a handful really delivers and even then some of them are not properly supported or maintained. They also tend to conflict sometimes.
I will not recommend anything for project management specifically but these are the ones which made our live so much easier:
TagsPlugin - the most useful one, adds tags support
BreadCrumbsNav - show previously visited pages, saves lots of time
ShowPath - show the breadcrumbs path, useful if you have your pages named hierarchically
CaseInsensitiveWiki - allows entering case-insensitive URLS
Stratistics - show Wiki/SVN statistics
WikiRename - allows page renaming (does not work well with the Tags)
0.10
WebAdmin - pre-installed in 0.11 but before you need to get it separately
My Favorites:
General:
Better editor WYSIWYG: http://trac-hacks.org/wiki/TracWysiwygPlugin
TicketCalendar Macro: http://trac-hacks.org/wiki/WikiTicketCalendarMacro
AccountManager: http://trac-hacks.org/wiki/AccountManagerPlugin
Scrum
- Agilo: http://trac-hacks.org/wiki/AgiloForScrumPlugin
This is the place to watch http://trac-hacks.org/
Besides those already mentioned here, I also found the following necessary:
Announcer - very flexible notification scheme
AutocompleteUsers - handy while typing (existent) user name
AutoLinks - automatically make words not conforming to wiki naming rule but matches existent page name a link
CustomFieldAdmin - make manage custom fields easier
Redirect - handy if you constantly need to make short-hand name wiki pages (like HTML redirects to HyperText .....)
TicketDelete - make deleting, if at all needed, easier
WikiRename - must-have for wiki refactoring
Below are good-to-have:
S5 - directly render wiki pages as slideshow in S5 format, could be really useful for using Trac as the source for presentation
FullBlog - add blogging support to Trac
Vote - cool add-on feature for big team
TracWikiToPdf - transform wiki page to pdf dynamically (however the effect might be all that satisfying)
TimingAndEstimation - neat for tracking time and/or estimation
I really like the BatchModifyPlugin that makes it easy to change more than one ticket at the time.
MasterTicketsPlugin is quite useful for ticket dependncies.
I would recommend against Bitten for CI (Continuous Integration) (see Martin Fowler on the subject) although I am using it.
The task force behind Bitten doesn't seem strong enough to process the remaining tasks. Simply look at the age and the number of posts in Bitten tickets
I don't admin our Trac, and I don't know all the plugins we use. But I co-developed a GUI we use to navigate the tickets and to track time spent on specific ones. It uses the xmlrpc plugin to query ticket information and to write some information back. Extending Trac is really easy this way.
my must-have list of plugins:
http://trac-hacks.org/wiki/AccountManagerPlugin
http://trac-hacks.org/wiki/GitPlugin
http://trac-hacks.org/wiki/TagsPlugin
http://trac-hacks.org/wiki/BatchModifyPlugin
http://trac-hacks.org/wiki/TicketDeletePlugin
http://trac-hacks.org/wiki/XmlRpcPlugin
some may be part of trac since 0.12
and a script:
https://subtrac.sara.nl/oss/email2trac
Apache Bloodhound is a collection of plugins bundled with Trac. It includes some of the individual plugins suggested in earlier answers, like the AccountManagerPlugin.
The major plugins developed as part of Bloodhound are a very robust Multi Product implementation, full text search (based on Whoosh) with better navigation.
Ticket relations have also just been added.
Bloodhound keeps integrating newly released trac versions quickly, and all plugins interoperate as expected because they're purposefully bundled. It's also still compatible with most trac-hacks.
What plugins you will consider must-have depends heavily on your use case.
Must-have plugins if you need more power in creating advanced wiki pages:
GraphvizPlugin
WikiExtrasPlugin
Must-have plugins if you like IDE-style auto-completion and indentation features in the text editor:
TextareaKeyBindingsPlugin
WikiAutoCompletePlugin
Must-have plugins if you use many Mercurial repositories:
MercurialPlugin
HgDirManagerPlugin
Must-have plugins if you ...
... want to archive emails: MailArchivePlugin
... want to track time spent on tasks: TimeTrackingPlugin
... want to plan your week: WeekPlanPlugin
... want to drag cards between stacks: CardsPlugin
...
But if you don't have these use cases, you will not find the plugins valuable.