After profiling the database and enabling changetable logging, I determined the location of the data. It is actually stored in an XML snippet in the propertytext table. This lets me pull for a specific project:
select propertyvalue from jira.propertytext pt
inner join jira.propertyentry pe on pe.id = pt.id
inner join jira.project proj on proj.id = pe.ENTITY_ID
WHERE pe.ENTITY_NAME = 'Greenhopper'
AND pe.PROPERTY_KEY = 'CONFIGURATION'
and proj.pkey ='DR'
I then just need to add in the XML parsing text. The values are stored as BURNDOWN_START_DATE_XXXXX and BURNDOWN_END_DATE_XXXXX where XXXXX is the ID of the version in the projectversion table.
If you use the new board of Agile :
Greenhopper does not use Fixversion anymore to handle the sprint. They are separated fields now.
So projectversion = version in Jira
_Sprint table is the sprint which are not a version anymore.
If you use the classic board, yes its still fix version and the information are stored in the table
A0_XXXXXX_VERSION for the start date related to the version_ID of projectversion so for the classic board you would use something like :
SELECT * FROM AO_60DB71_VERSION gv, projectversion p where p.ID = gv.version_ID
Actually, when I use Greenhopper to create the fixversion, it allows specification of the start date and end date and the release date. I misstated about the complete date. The release date is actually in the projectversion table. I thought perhaps the SPRINT table might include the start/end dates since I've used that to get sprint data but it only has the true sprints, not the fix version information. When using the classic view, the information is definitely shown. FYI, Jira 5.1.1 and Greenhopper 6.1.1.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot