Fetch milestones from sourceforge net
nijel opened this issue · 4 comments
Manually typing milestone is not really helpful, the list should be fetched from sf.net and user should just choose from that. Ideally the value would be prefilled based on versions where the error was found.
I'm working on this currently. And here's how I'm planning to implement it.
- Maintain a separate table on error-reporting-server which serves as cache between SF.net and error-reporting-server. The schema of the table would be as follows.
| Field | Type | Description |
|---|---|---|
| type | string | field type (milestone, status, tags etc) |
| value | string | value of the field |
| created at | time stamp | when was it created |
| updated at | time stamp | when was it updated last |
- Create a drop down for milestone field from the cache table in
app/View/SourceForge/create_ticket.ctpin place of a input text. - Provide a refresh button on the right side of that drop down list for Manual Cache Update. Clicking on that updates the mentioned table. Updating can also be done periodically via a cron job.
- On the Create Ticket form warn user if cache is older than some time X. Recommend the user to refresh the cache by clicking on that refresh button.
- Updating
- Fetch all the milestones from SF.net.
- Insert them to cache table.
Please provide your valuable suggestions on my approach described above.
Now, everything is fine except fetching milestones from SF.net. I read the documentation of Allura API but could not find a way to fetch values of a particular ticket field.
I even tried getting that info by submitting milestone=null in hope that it would return error message providing all the permissible values, but it doesn't. It creates a ticket even without milestone (See Ticket 4475 and 4477 ).
I'd not include button for manual update, I'd rather do it using cron job only. But as SF.net does not export it, it's probably not relevant :-).
Hmm thinking more about milestone, it should fill it automatically based on the version(s) submitted. The milestones always include first three version numbers, in case the version is -dev, it should prefix Latest_Git and that should handle most cases without even fetching the data from sf.net....
Okay. Right now I'm not implementing the "fetching from SF" feature.
Working on the suggestions of filling the value automatically based on versions right now. Will create a pull shortly.
- Assign value to milestone field automatically from
pma_version. See Pull#55.