62 Commits (e10ef311e35ae202eefdd5c59be41ab1e23d57cc)

Author	SHA1	Message	Date
friflaj	f1e7231d39	Migration requested version_id twice, shifting everything one position	14 years ago
friflaj	85567ad652	Doesn't really matter whether we've selected the backlog, just show the link	15 years ago
friflaj	5b9fd88518	disentangled migrations ... Unfortunately these tow migrations cannot be ran one after the other; migration 009 causes an after_save to fire which touches a table only available in 010. I see no way around this other than to merge these two. #rubyonrails concurs.	15 years ago
friflaj	9182bfc29a	handling non-null just makes things harder. The burndown method ... filters them out anyway.	15 years ago
friflaj	25ae9d3235	renamed start_date, burndown generation, parameter quotation ... * start_date was added to the core Issue model, overriding our start_date. The core start_date is just an alias for the effective_date, so it's not useful to us. * burndown generation. Sprint.generate_burndown will generate the burndown for all current sprints by calling +generate+ on each of them. +generate+ picks what it can from the cache and interpolates the rest. The cache can be primed by just calling +generate+ at least once a day. Calling it multiple times will have no effect _unless_ you've changed a story or task, which will cause today's cache entry to be discarded. This way you will always have the latest data. The charts being generated: - points committed: the total of points included in the sprint. This would typically always be the same from the start, but will change if stories are added or removed mid-sprint - points resolved: when a story goes to 100% completed (typically by setting its tasks to closed), the story is deemed resolved. - points accepted: when a story is closed, it is deemed to be accepted by the PO - remaining hours: total of hours remaining on all tasks - required burn rate in points/hours: the number of points/hours the team will have to burn down each day to complete all the work at the end of the sprint. A flat line is perfect, if the line starts dropping it means the team is ahead of the curve, if the line starts climbing it means the team is running behind * parameter quotation added to raw sql	15 years ago
friflaj	e116d5b562	Migration cleanup	15 years ago
friflaj	1d82a855f5	raw sql executes fail when the transaction is still open	15 years ago
friflaj	1958e8866a	migration failed when the plugin wasn't already configured	15 years ago
friflaj	0874c70ae8	Migration for relaxdiegos' redmine_backlogs	15 years ago
friflaj	64e468d50b	Story point editing	15 years ago
friflaj	1f6764a016	Initial checkin	15 years ago
Mark Maglana	3e30a8a49a	- Fix migration sequence	15 years ago
Mark Maglana	217d2c42b0	- First import into new repo	15 years ago