3 answers

1 accepted

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...