Bug Report Shadow Database Planning

Registered by Chris J Arges on 2012-04-12

Rationale:
Multiple teams are working on reports using .json files obtained from Arsenal. We're looking for a better way to maintain a stateful, historical bug database without stressing the launchpad server.

Goal:
Agree in a way of persisting launchpad data "locally", being that the source of data for reports. Implement that.

Blueprint information

Status:
Complete
Approver:
Kate Stewart
Priority:
High
Drafter:
Chris J Arges
Direction:
Approved
Assignee:
Chris J Arges
Definition:
Approved
Series goal:
Accepted for quantal
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-12.10-beta-1
Started by
Kate Stewart on 2012-05-22
Completed by
Kate Stewart on 2012-09-12

Related branches

Sprints

Whiteboard

What is needed / Use-cases:
- System to fetch data for data-mining and report making for various teams.
- Needs to handle large queries reliably and effeciently.
- Needs to handle many fields and able to add more fields if needed.
- Need to handle private and public bugs
- Need to have multiple tables (people table / tag table / etc).
- I would like to use arsenal to gather bug data to show a report of affecting bugs.
- I would like to gather a historical view of bugs and extract relevant features for my team.
- I would like to extract secondary features and query for these easily.
- I would like to gather bug totals for particular types.

What is already available?
- Arsenal
- bug-timetracker
- quality-dashboard

How should we approach this?
- If an existing project can be extended to accomplish these tasks, then we should use it. Otherwise we should create a new project.
- Should we use json/database, if database what type of database?

(?)

Work Items

Work items:
[kate.stewart] (arges) write use-cases / requirements in blueprint : DONE
[arges] (brian-murray james_w) Look at launchpad code, look at database generation .sql file. : DONE
[ursinha] - investigate proper ORM to use : DONE
[arges] - investigate bug-timetracker/quality-dashboard to see if this code is what we need : DONE
[arges] - start writing script to grab data from launchpad : DONE
[arges] - determine what machine/software requirements are needed (if any) : DONE
[arges] setup project under arsenal - name shadow-database : DONE

Dependency tree

* Blueprints in grey have been implemented.