JIRA Charting Plugin

How about Burndown Chart generation, similar to this agile plugin?

http://paloalto.laughingpanda.com/mediawiki/index.php/Agile_Plugins

This is excellent - my management has been screaming for trend reports. Will be installing and configuring asap.

Couple questions:

Am assuming that the Resolution Date field must be added to all issue forms/contexts.

1. If so, how does it get populated? Does the closer have to pick the res date for each issue?

2. Any way to populate this for "pre-plugin install" data?

3. Please confirm that this report does NOT look at the out-of-box Resolution field value. We have added a couple of workflow steps after Resolve (QA Verify-Close and UAT Verify-Close) but not added new corresponding resolution values. Hence a bug that has been fixed but not yet tested and closed will already have "Resolved" in Resolution field, rendering these reports less useful.

We're very excited about this plugin -- thanks and keep up the good work!

Love the new plug-in - I have been doing a manual SQL, exporting to Excel, and making the charts - glad I don't have to do that anymore!

We have imported quite a few issues from an old system. When those imported, they didn't get a change history, so the resolution date is not available. I can see that these don't have the resolution date set, but how will it affect the charts when you are counting resolved issues?

Thanks!

Jami

Would it be possible to add reporting on the number of issues that are reopened (possibly in conjunction with the Created vs Resolved Issues chart) or does the resolution date field limit this to only reporting on the current status?

Are reopend issues counted as newly created in these charts or do issues only show up as created once?

Regarding errors seen on just 2 of the 3 reports (Resolution Time and Created vs Resolved): I had the same problem and believe it is caused by "proactively" creating the custom field BEFORE installing the plug-in.

To fix:

Delete your original new field.
Create it again -- this time Type: Resolution Date will be an option. Select that, name it and save.
I did not assign it to any screens - you may if you like, but that may make it editable.
Re-index.

To verify that the dates have been populated by the re-index:
Go to your issue navigator.
Configure/add new column: Resolution Date to your navigator
Select "Back to navigator" link.
You should now see dates in that column and the charts will now all work correctly.

-- Might want to tweak the install instructions to emphasize that you can/should create the custom field only after installing the plug-in, and/or mention that the type Resolution Date is added during install.
 

Hi Mike,

nice plugin !

Will there be a german version in the near future ? 

Pie Charts! It would be great to see an extension to the Single Level Group By Report that will display a pie-chart of the filter results, broken down by the chosen field.

Hi everyone,

I have a perhaps small problem. I am running JIRA on AIX 5 with Oracle and a Tomcat 5.5 server.

I have installed the plugin and now I have two issues:

1.) I dont see the custom field on the issue page 

2.) When I start one of the new reports I get an error:

Could not execute action [ConfigureReport]:org.jfree.chart.JFreeChart<p><small><small><pre>java.lang.NoClassDefFoundError: org.jfree.chart.JFreeChart at java.lang.J9VMInternals.initialize(J9VMInternals.java:114) at org.jfree.chart.ChartFactory.createBarChart(ChartFactory.java:570) at com.atlassian.jira.ext.charting.jfreechart.ChartUtils.generateBarChart(ChartUtils.java:86) at

and so on...

Do I hve to install something else on my AIX machine?

Thanks for any answers.

By from the other side of the world (Germany)

Thomas 

Mike? Hey, I see bug reports regarding a problem that I have, but no comment on it.
When I re-index, the console throws tons of exceptions (I can give you the dump if you want), and basically, indexing fails and I get an empty project (-: after removing the chart control and re-indexing it all goes back to how it was (thank god! I almost had to take an oxygen tank!).

 Is this a problem you know how I can solve? what I am dowing wrong? using sql server BTW...

An excellent extension to JIRA - one that adds a whole new level of capabilities. People at work have see the graphs on our Test Server and have asked when we're putting JIRA 3.5 into production. Thank you.

You wrote: I'm always looking for suggestions of new charts to add to this plugin

So, here our our suggestions for improving an already great tool.

For all graphs

(a) Specify range in terms of # periods. Eg, 12 months or 52 weeks; It seems kinda odd to allow "Quarterly for 100 days". 

(b) On a lot of the graphs we end up with nothing useful on the X axis - just a whole bunch of dots. Makes it harder to see what the timespan is.

Graph Specific: "Average Resolution Time"

Great graph, really useful.

We found, however, that we had to drill down a bit to understand what was going on. We had an enormous spike (long resolution time) for one month, but when we drilled down, found that this was because a bunch of extremely old issues were finally being addressed by an external vendor. So, the spike was good!

Could you add a line to the graph, showing the average age of unresolved issues over time? This would allow for some interesting analysis without having to drill down. If the bar went above the line, the issues closed were mostly older ones; if the bar went below the line, the issues closed were newer ones. Having this line would have helped us understand our spike. Also, the trend of the line (up or down) would help in managing our backlog.

Another idea - what about having some stacked bars to show the distribution of ages of the issues resolved? The total height of the bar would be unchanged, but broken down (say) into four groups: Resolved within 7 days,  Resolved within 30 days, resolved within 90 days, resolved over 90 days. It would be harder, but possibly the breakpoints could be configurable ...

New Graph: Age of Open issues

Generate a bar chart with date on the x-axis and count on the y-axis showing issues from a given filter (or non-closed issues for a project), grouped by their creation date. This allows a simple way to see the age distribution of issues that need to be addressed.

Perhaps this could be a stacked-bar chart, with each bar broken down - by status or priority.

We currently generate graphs of this kind with Crystal Reports as a part of monthly reporting - having them available in real time within JIRA would be really cool.

New Graph: Pie Charts

Break down the results of a filter by status or priority.

Does this plugin work with Sun JDK 1.5.0_06 ?

A user who had some trouble getting the charting plugin working says:

Before installing this plugin, make sure
that thumbnails work. If they don't, then run ldd on libawt.so in your
Java installation to see which X libraries aren't present (fc4 may need
the libs in xorg-x11-deprecated-libs-6.8.2-37.FC4.49.2.i386.rpm). Also
check your DISPLAY environment variable.

I posted on the JIRA-dev forums, but I'm posting here because it's more appropriate.

I would like to have a report and graph a chart indicating the number of currently open bugs on each date of a given date range. This is not the number bugs which were created on each day(the "Created vs Resolved" and "Recently Created Issue" can do those).

Original post here: http://forums.atlassian.com/thread.jspa?threadID=9900&tstart=0

Hello,

First of all, from description, plugin looks awesome, thank you for it. Unfortunately, something seems to go wrong when I try to work with this plugin (windows, complete installation from scratch of the latest version). I placed plugin jar file as directed, created  Resolution Date field, re-indexed JIRA.

 1. I do see report, but it is empty - straight line.

2. Resolution Date field, appears in Browse Issues screen, and has no values

3. Resolution Date field is not visible in any other screen.

Please advise on how to resolve this, or what diagnostic steps are needed to provide more information.

Thank you,

Konstantin 

A small typo in the Usage & Installation instructions.

Where it says 'make sure the searcher is set to "Date Picker"', it should say Date Range Picker.  At least that's the only option I see available.  I'm still installing it so I don't know how well it runs yet.

However, as Konstantin mentions above, even though I assigned this custom field to the Resolve Issue screen (which should show up when I resolve or close an issue), I don't see it there.  Maybe it's "auto-magic" and therefore invisible?  I haven't tried running a graph yet, but I'm guessing maybe I need to resolve some issue first, then it'll show results?

An enhancement suggestion/request, if I may?

On the Pie Chart, when I select Statistic Type and choose Component, I'd like a way to exclude sub-tasks.  I realize I could build a filter for this, but if I'm trying to chart tasks for a given project, so I'm selecting the project name from the Project or Saved Filter drop-down list.  In order to exclude sub-tasks via filter, I'd need one filter per project.

A possible solution I see for this might be a checkbox on the selection screen to allow you to limit the graph to the currently-selected project, then you could select a "no sub-tasks" filter.

Thanks!

The pie chart is great. Good job !

From our perspective, the obvious next nice improvement would be to add the time factor over it.

We're working on a feature driven based development process, and such view would be really usefull.

Thanks!

Vince

I have tried to install this on Jira 3.6.3, and all the new custom field types are available, except the Resolution Date one.

Instead I have the following message in the log:

2006-11-14 20:42:34,066 ERROR [jira.issue.managers.DefaultCustomFieldManager] 
Could not find any custom field value with key 'com.atlassian.jira.ext.charting:resolutiondate'.

It appears that the message has occured for a long time in our Jira installation. So I guess somebody has tried the plugin then removed it...

We also have this message for de.phil.jira.plugin:searchableattachment, that belong to a plugin that we have removed, and for two custom field we have coded ourself, but that are still there and working.

So I guess that our custom field list is corrupted. How could we fix that?

How would Atlassian recommend obtaining the following graphs?

1. x-axis time, y-axis number of bugs, one line per component

2. x-axis time, y-axis number of bugs, one line per status

These are commonly requested graphs.

 ~Matt

Jed,

Thanks for the feedback. Yes,  it's compelling sounding because every employer that I install Jira for wants it, and is surprised that Jira can't provide it

So, does Atlassian have any recommendations for existing OLAP systems to generate such graphs?

~Matt

Yeah, I've done a few of those myself.

For completeness, please would you describe how one can use Excel/Access to generate such graphs. I get the "export my entire project as Excel", but I don't see how this let's one group events into time-based plots, or why Access comes into this. I guess it's a matter of parsing the table of events from day zero to aggregate the information for the graph.

Is some developer able to provide also for the JIRA version 3.7 beta 2 the corresponding plugin jar 1.2.13?

Cheers,
Alexander

Um, yeah. Looks like this has a dependancy that's broken.

[Closure - Resolution Fields & User or Group Tracking Report Plugin] appears to be required for the Resolution Date custom field. Any workarounds??

Hi,

Version 1.3.5 is in your version list, but not downloadable yet. 

Thanks,

 Marc 

We've just upgraded to 3.8. Does anyone know if this is compatible with 3.8?

Thanks 

Any idea when 1.3.5 will be released?

The required field of type Time In Status shouldn't be in the search mask because I guess that no one can really use is for the search of issues. This field is much more a source of irritation in the search mask.

As requested by others also please upload 1.3.5! You have added it to your version list!

Yes, please post 1.3.5. We are upgrading to 3.8 but don't want to do so without this.

I got "Error: No resolution date custom field found. This custom field needs to be added to run this report." on Resolution Time Report.  All required custom fields are already there including Resolution Date custom field.

May I also ask which maven goal should I call to build 1.2.13 to work on JIRA 3.7.4?

Regards,
Jerry

Hello,

I already upgraded to Jira 3.8.1.

The charting plugin 1.3.5 works at first glance.

Until now I only noticed that the numbers of issues disappeared from the pie chart. Bug or feature?

Cheers

Bettina Zucker 

It would be really nice if the charting portlets allowed for a free text title to be provided along with the parameters. This would help in distinguishing charts (E.G. two pie charts with different parameters one for resolution and another for status) that I might want to include side by side on a dashboard with an appropriate chart title.

 Cheers

Mahadevan

My organization is using Jira 3.6 Enterprise, and as such I went ahead and deployed the 1.2.11 Charting jar. I can see from the functionality and screenshots, however, that I might be missing some of the latest functionality.

Am I able to save executed charts to a Dashboard in 1.2.11?

Would I be able to use release 1.3.5 (or any other release that supports adding to Dashboard for instance) within Jira 3.6 (#153)?

Thanks in advance!

-armen

Hey,

Is it possible to create a chart and then link directly to the image from another web page on some other server? A single URL could contain all necesarry parameters and respond with a chart image?

-dennis 

Ideally, the plugin should be built into the WAR file if not running standalone, instead of dropped into the running WEB-INF/lib directory, so if the WAR file is rebuilt, the plugin doesn't disappear (this seems to be standard operating procedure with all the rest of the plugins).

Hello, i have install this plugin, but i have a brother (mozilla or Ie 6) in english, my jira is in english UKbut the label name of reports in BROWSE PROJECT are in french language ...  Have you a solution for change this Label ?

thank's.

Yannick 

Hello, i just installed the plugin, but cannot see any charts (neither as a portlet nor in the issue navigator => "diagrams").
When trying to display a chart via issue navigator => diagrams i only get a greyed-out-screen.
Inspecting the console window i see the following error

19:48:53,627 ERROR [Engine] ----- Root Cause -----
java.lang.NoSuchMethodError: org.jfree.chart.ChartFactory.createPieChart(Ljava/lang/String;Lorg/jfree/data/general/PieDataset;ZZZ)Lorg/jfree/chart/JFreeChart;
at com.atlassian.jira.ext.charting.jfreechart.ChartUtils.generatePieChart(ChartUtils.java:447)
at com.atlassian.jira.ext.charting.data.DataCollector.populatePieChart(DataCollector.java:664)
at com.atlassian.jira.ext.charting.charts.singlefieldpie.SingleFieldPieChart.getViewHtml(SingleFieldPieChart.java:57)
<...snipped...>

Restart of JBoss didnt help.
Restart of PC didnt help.

We are using

• JIRA Professional Edition, Version: 3.10.2-#262
• jira-charting-plugin-1.3.9.jar
• JBOSS 3.2.3

Thanks for any ideas to resolve this...
Christoph

Hi! I have a problem..

     I installed the jira calendar plugin in version 3.10 of Jira. When i tested the reports i notice that the "Created vs Resolved Issues Report" doesn´t work, i mean , it only shows

the created issues but not the resolved issues (the table shows 0 issues resolved too).

     I don´t know if that happens because i change the workflow and create new steps (i have a step called "Resuelto" that has a link with the

Resolved status like in the original workflow and other steps linked to their corresponding status). 

     The same happens in the "average time in status" and "average number of time in status" reports, it´s like it doesn´t recognize the statuses.

The only report related with statuses that works it´s the pie chart with the attribute "Statistic Type" = Status.

Any idea??? ....Thanks for your help!

Hi,

Is there any diffeence between 'Date Picker' and 'Date Range Picker' ?

As I'm trying to create custom field  'Resolution Date' but in the 'Search Template' I'm not getting option for 'Date Picker'.

Jira Version 3.11

Thanks,

I wonder if this is still actively maintained.

I think this is a very useful plugin for JIRA but there are a lot requests for new or improved functions like e.g. burndown charts or

open vs. resolved charts for a given time period or iteration (JCHART-184),that do not seem to be too complicated to implement.

Also there are some important bug like the translation error (JCHART-171) that makes is unusable is certain situations.

It would be good if someone could at least comment these issues, whether they are considered to be looked at in the near future, whether there are known workarounds, etc.

Thanks,

-Torsten

Hi,
What I've seen so far is great, though I wouldn't feel comfortable giving each and every user the chance to produce charts for fear of reducing performance or destabilising JIRA.
Is there a way to restrict use of the charts feature to certain users or groups?

kind regards,
Paul

does anyone have a version of this with the burn down chart compiled already for 3.12.1?

If so would you mind sharing?

All my reports have been wokring except Pie Chart. I have been using Jira version 3.8 and plugin version1.3.4 Could someone please help me....I am getting following error:

HTTP Status 404 - Could not execute action [ConfigureReport]:org.jfree.chart.plot.PiePlot.setSectionOutlinePaint(Ljava/lang/Comparable;Ljava/awt/Paint;)V<p><small><small><pre>java.lang.NoSuchMethodError: org.jfree.chart.plot.PiePlot.setSectionOutlinePaint(Ljava/lang/Comparable;Ljava/awt/Paint;)V at com.atlassian.jira.ext.charting.jfreechart.ChartUtils.setSectionColor(ChartUtils.java:466) at com.atlassian.jira.ext.charting.jfreechart.ChartUtils.generatePieChart(ChartUtils.java:454) at com.atlassian.jira.ext.charting.data.DataCollector.populatePieChart(DataCollector.java:664) at com.atlassian.jira.ext.charting.data.DataCollector.populatePieChart(DataCollector.java:622) at com.atlassian.jira.ext.charting.charts.singlefieldpie.SingleFieldPieReport.generateReportHtml(SingleFieldPieReport.java:49) at com.atlassian.jira.web.action.browser.ConfigureReport.doExecute(ConfigureReport.java:96) at webwork.action.ActionSupport.execute(ActionSupport.java:153) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:209) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:51) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55) at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:182) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.LoginFilter.doFilter(LoginFilter.java:181) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132) at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:41) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.johnson.filters.JohnsonFilter.doFilter(JohnsonFilter.java:91) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.gzip.GzipFilter.doFilter(GzipFilter.java:72) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) </pre></small></small></p>

We just installed this plugin and have not been able to get it to work.  The default pie-chart will show up after pressing the chart icon in the issue navigator, but I am not able to configure it.  I receive a small progress bar that never stops spinning.  We have Jira 3.12.1..  Any ideas?

I am unable to get "Created vs Resolved" working. All my issues are either in open state of closed state. The ones in closed state had passed through the resolved state before. The resolution date also is visible in Issue Navigator.

But the chart always shows 0 items for resolved

Is it still possible to get hold of older versions of the Charting plugin? We're running Jira 3.10.1, and upgrading to 3.12.2 would be quite a big deal for us without a huge amount of benefit, so I really want to install plugin version 1.3.9. I'm sure it was accessible from this page somewhere a couple of weeks ago, but can't find it now.

Thanks
Neil

I added the plugin, the custom fields and I reindexed the data but none of the custom fields got populated.

 PLease advise. I Have jira 3.11 and jdk 1.6.0_03.

Thanks,

Simona 

does anyone know an effective way to track reopen tickets?  I can set up a filter to find all reopen tickets, but that only finds the tickets that are reopen at that particular time.  If I use the created vs. resolved report in conjunction with the reopen filter that I setup, is the "created" line essentially the reopen count for any particular day?  Is it a way for me to tell how many reopen tickets there have been over the last X days/months???

Hi All,

Can you please let us know, whether this plugin would work in Confluence also.(cause we cant create these customf field so is there any otehr option)

Or advice is there any other plugin with the same functionality and can be used in confluence ?

Regards.

Hi ,

    I can not find the "Burndown chart" in this plugin!Does it include in it??Wait for your help,Thanks!

I really like the "Created vs Resolved" issues report. I would like to see this style of report for any two filtered result sets.

For instance, I'd like to create one filter of all "In Progress" issues. And another filter that would show all "Open" issues. The concept is the same, except instead of having two status hard-coded in chart, the chart would just display one group of filtered results over time, vs another set of filtered results over time.

Another example, one manager here wants to show this graph, but just display "Closed" issues vs "Not closed" issues. (He doesn't care if the issue is Resolved, he wants to know that it has been resolved, and verified by QA, and then closed). This graph could be created if I had the ability to show the results of two filters in the same graph.

If there is any way of doing this now, I'd be happy to hear about it. Otherwise, if there is any intent on doing something like this?

Thanks,
-Dan.

I have created a new version of this plugin using the ideas of the 'pending' chart written by Pierrick Perret (http://confluence.atlassian.com/display/JIRAEXT/Charting+Plugin+++Pending+feature?showComments=true&showCommentArea=true).

I based this plugin on the official v1.3.13 version of the atlassian plugin. Instead of 'Pending' I used the word 'Unresolved'. I put all of the 'unresolved' options within the 'createdVsResolved' chart and added the ability to have created and resolved numbers represented by 'bars' instead of 'lines'. The jar can be downloaded from:

https://maven.atlassian.com/contrib//com/atlassian/jira/ext/charting/jira-charting-plugin/1.3.14/jira-charting-plugin-1.3.14.jar
I need to check with Atlassian for the proper process of getting approval for making this an Atlassian 'supported' version of the plugin. The charting resources are all working on the next release of the charting plugin v1.4 and so no more changes are planned for this release.

 http://www.capitalcityconsultants.com

I'm sure that I've missed something basic, but this new feature is not working for me.  When I select the Unresolved type and then chose my project.  On my dashboard I get the message: portlet.pending.nochart.  In the area where I would expect to see the title I get: portlet.pending.name: poirtlet.pending.anonymousFilter.

 ideas?

Hi, I posted a bug report here: https://support.atlassian.com/browse/JSP-19560&nbsp;& http://developer.atlassian.com/jira/browse/JCHART-134

and they said it was fixed in version 1.4, but is version 1.4 of the plugin released yet, and is it compatible with 3.12.2?

Regards,
Paul

I am using plugin version 1.3.13 and it works great with configuring pre-set portlets. But I am not able to chart and save my own filters. From the error it seems like I am missing some configuration (classpath?). Thanks in advance for your help!

Here are the steps I have follwed.

1. Deployed 1.3.13 on JIRA version 3.12.3 #302

2. Added 3 custom fields and ran reindex

3. I see Charts option for each of my filter results which is great!

4. Clicking the Charts link on any filter results page shows default pie chart correctly but when I click Configure it gives me following error.

5. Same thing when I click Save button except it fails on (AddPortletToPortal) 

HTTP Status 404 - Could not execute action [SavePortletSearchViewConfiguration!default]:Action 'SavePortletSearchViewConfiguration' not found or could not be initialized: java.lang.ClassNotFoundException: SavePortletSearchViewConfiguration<p><small><small><pre>java.lang.IllegalArgumentException: Action 'SavePortletSearchViewConfiguration' not found or could not be initialized: java.lang.ClassNotFoundException: SavePortletSearchViewConfiguration
    at webwork.action.factory.JavaActionFactory.getActionImpl(JavaActionFactory.java:64)
    at webwork.action.factory.ScriptActionFactoryProxy.getActionImpl(ScriptActionFactoryProxy.java:54)
    at webwork.action.factory.XMLActionFactoryProxy.getActionImpl(XMLActionFactoryProxy.java:54)
    at webwork.action.factory.PrefixActionFactoryProxy.getActionImpl(PrefixActionFactoryProxy.java:102)
    at webwork.action.factory.JspActionFactoryProxy.getActionImpl(JspActionFactoryProxy.java:53)
    at webwork.action.factory.CommandActionFactoryProxy.getActionImpl(CommandActionFactoryProxy.java:62)
    at webwork.action.factory.AliasingActionFactoryProxy.getActionImpl(AliasingActionFactoryProxy.java:96)
    at webwork.action.factory.CommandActionFactoryProxy.getActionImpl(CommandActionFactoryProxy.java:53)
    at webwork.action.factory.ContextActionFactoryProxy.getActionImpl(ContextActionFactoryProxy.java:36)
    at webwork.action.factory.PrepareActionFactoryProxy.getActionImpl(PrepareActionFactoryProxy.java:37)
    at webwork.action.factory.ParametersActionFactoryProxy.getActionImpl(ParametersActionFactoryProxy.java:46)
    at webwork.action.factory.ChainingActionFactoryProxy.getActionImpl(ChainingActionFactoryProxy.java:52)
    at webwork.action.factory.DefaultActionFactory.getActionImpl(DefaultActionFactory.java:125)
    at webwork.action.factory.ActionFactory.getAction(ActionFactory.java:63)
    at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:120)
    at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:211)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:73)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119)
    at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55)
    at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:192)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:120)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:125)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132)
    at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:43)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:50)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:79)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
    at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200)
    at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
    at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773)
    at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)
    at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
    at java.lang.Thread.run(Thread.java:619)

Hi,
 
Are there plans that automated emails or notices sent whenever issues based on certain conditions changed? For example, send email if an issue has not been touched in x number of days. it's a reminder to the assignee that the issue is there. Or that a reminder is sent when an issue is about to reach a due date or number of days?
 
Thanks
 

Hi,
 
Are there plans that automated emails or notices sent whenever issues based on certain conditions changed? For example, send email if an issue has not been touched in x number of days. it's a reminder to the assignee that the issue is there. Or that a reminder is sent when an issue is about to reach a due date or number of days?
 
Thanks
 

Which version charting plugin can use in jira 3.7, please help me, thanks lot.

Hello All,

I've been trying to install the plug-in, but when I try to add the custom field, I can't find the Resolution Date type.  I only see the Date Picker type and a Datetime type.  Can anyone tell me what I'm doing wrong?  I'm running Professional Edition, Version: 3.12.3-#302.  Any help would be greatly appreciated.

-Jing