Type:
Feature
Priority:
Major Major  
State:
Open
Subsystem:
Unknown
Reporter:
Jacques Morel (jacmorel) Send Email
Assignee:
<no user>
Affects:
No affected versions
Fix for:
Backlog
Created:
21 months ago (09 Feb 2007 09:06)
Updated:
8 months ago (06 Mar 2008 13:40)
Votes:
0
Resolved:
JIRA source:
TW-1673
No attachments

<Warning>this issue is really an epic</Warning>


TC keeps (or will keep) all the necessary aspects of a project health.
Presenting a view that summarizes all these and give a trend graphs and summary status on each would help tremendously keep projects under control.
Visibility to that data is crucial to the good execution of a project.


Graphs could show a short term and long term view (long term is needed for strategic tracking, short term to drive improvement day to day).
The summary status would give a green, yellow, red type status on each aspect and on the overall health.
Look at the competition (like agitar's at http://www.agitar.com/openquality/hibernate2/index.html or CodeReport) for inspiration


That view would need to be customizable with plugins to integrate new aspects/reports.
Reports could cover many aspects:
1. internal quality like
1.1 coverage (corbutera, clover, emma)
1.2 package design (jdepend, macker)
1.3 duplication (PMD, IDEA duplication)
1.4 code analysis (CheckStyle, FindBugs, IDEA inspections),
1.5 continuous integration (TC future 2.0 CI reports... ) or
1.6 review rate (crucible,
2. external quality like
2.1 bug trends (integrating with jira, bugzilla, clearquest...)
2.2 plan status (integrating with versionone, rally, xplanner...)
2.3 documentation trends (integrating with confluence, jforums...)


(Look at http://www.intellij.net/forums/message.jspa?messageID=5181475#5181475 and http://www.jetbrains.net/jira/browse/TW-1665 for some background around how different reports could be integrated).


Most of these reports generate their raw data in xml and then style them into (sometimes multi-page) html reports. Using a set of xpath expression, the relevant data could be extracted from the xml and stored with each build to be used in the dashboard. A flexible graphing engine would then be used to generate graphs. Threshold setting could be used to generate the summary status.


Note: Portlet support might be handy here as some of them may already have portlet to embed.

  • Dimitar Dimitrov (ddimitrov) Send Email
    19 months ago (12 Apr 2007 11:57)
Old New
Jacques Morel (jacmorel) - 8 months ago (06 Mar 2008 13:40)
Assignee sashka (sashka) <no user>

JetBrains Tracker revision #2008 [13-Nov-2008 11:56] (version #56) Copyright 2007-2008 JetBrains s.r.o.