51 Commits (cab2e9a808e4beb60369286c9cf83888f13509f2)

Author	SHA1	Message	Date
Jens Ulferts	81c0d3de36	removing position setting migrations, keeping the migrations as such to make it transparent	14 years ago
Jens Ulferts	5aeb056b6c	using "remove" instead of "drop" on down migration	14 years ago
Jens Ulferts	9f5d02ca11	correct default table name to correct table name in version_settings down migration	14 years ago
Jens Ulferts	ee454a8cca	#2891: creating table and specs for version_settings which will hold the display information	14 years ago
Gregor Schmidt	27b841407c	removing x-bits	14 years ago
friflaj	b54b17a8d2	Stupid rails	14 years ago
friflaj	35919d5bd5	Stupid rails	14 years ago
friflaj	c9aedbec5d	Don't break on nested tasks	14 years ago
friflaj	577596eb09	sqlite bombs out on the transaction stuff	14 years ago
friflaj	00ff75ec59	Task reordering must be done ordered by parent,position	14 years ago
friflaj	16103b8fc3	Treat task as story so we can remove it from the stories list	14 years ago
Emiliano Heyns	89e7a76da0	remove_from_list is not supported on Task anymore	14 years ago
friflaj	db7eb66a88	Fix for forum topic 12	14 years ago
Mark Maglana	b9a6b7ab1e	Fix positions	14 years ago
friflaj	76645c13d7	Fix for sqlite	14 years ago
Mark Maglana	6c222f3845	Additional tests to product owner role	14 years ago
friflaj	314271f2b4	Remove position from an issue when it is changed from a story into a task	14 years ago
friflaj	5985c77f7d	Looks like PG doesn't return the same row structure as mysql, explicitly picking columns now	14 years ago
friflaj	c660ddd1ae	comment cleanup, make sure 012 migration runs on clean postgresql ... database	14 years ago
friflaj	0bd0f3949f	Down-migration 011 missed sprint-start-date	14 years ago
friflaj	f632f43194	Add migration reversal for 011	14 years ago
friflaj	587903ba08	Move task order to nested_set ... The issues list will indent stories/tasks neatly if they use the nested_set ordering. It's functionally equivalent for us.	14 years ago
Mark Maglana	de6060f699	Fixing positions for unified story priorities	14 years ago
friflaj	509a531060	ActiveRecord execute sees fit to return _everything_ as a string.	14 years ago
friflaj	77d63df2c1	Legacy migration -- thank you James Dobson! ... Couldn't have done it without your legacy DB	14 years ago
friflaj	9d42d95b5c	Split legacy migration from schema creation	14 years ago
friflaj	3a0e63f55b	Can't request items on a non-legacy DB	14 years ago
friflaj	f17c7c1968	Another typo	14 years ago
friflaj	3e687a5373	Not all items had a position, and parent must be set before position on tasks	14 years ago
friflaj	c627b99c95	More informative abort message for the migration	14 years ago
friflaj	a89c93194f	I need to stop fighting ActiveRecord	14 years ago
friflaj	91dae6e83b	I need to stop fighting ActiveRecord	14 years ago
friflaj	d4e181aa63	Tree rebuild causes save on stories, which recalculation of derived attributes... which needs the tree to be present	14 years ago
friflaj	13e8e80cac	Damn stupid typos -- apologies!	14 years ago
friflaj	e80d89feb7	Legacy migration fixes	14 years ago
friflaj	bb33962771	test for parent, not parent_id	14 years ago
friflaj	bf4e1bf285	Drop items/backlogs table after migration	14 years ago
friflaj	eb53e1f3f6	Explicitly set root_id	14 years ago
friflaj	95ce5bfa40	Force plugin setup before migration	14 years ago
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