257 Commits (15f986ebcdf731451f2252dcca386f78691050c1)

Author	SHA1	Message	Date
friflaj	28421ed222	Have the sidebar chart follow the main burndown	15 years ago
friflaj	85567ad652	Doesn't really matter whether we've selected the backlog, just show the link	15 years ago
friflaj	38a9f6cc23	Show backlogs data in issues sidebar	15 years ago
friflaj	06afa473e3	Fix for project import	15 years ago
friflaj	712560bc90	Project importer simplification, and better problem reporting	15 years ago
friflaj	944054cbf9	Method 'velocity' renamed to 'scrum_statistics'	15 years ago
friflaj	e69804afb5	Add story points and estimated hours when a backlog is selected in the issues list	15 years ago
friflaj	576f36b77c	Yet more scrum statistics	15 years ago
friflaj	404c0a968c	Even more stats	15 years ago
friflaj	573fc9802b	Better stats	15 years ago
friflaj	46c2275495	Scrum statistics	15 years ago
friflaj	fcd52f6eaa	Fixes #243: divide by zero error in calculating project velocity ... Thanks to Mitch Shields	15 years ago
friflaj	2e46d59d1c	Sprint ETA	15 years ago
friflaj	773bdfff97	Velocity based estimate (#205)	15 years ago
friflaj	ac18532113	The queries panel only shows if you have custom queries, so I'm ... abusing the planning hook.	15 years ago
friflaj	52867f42c4	Added sprint impediments, removed story-as-task ... Story-as-task makes the taskboard impossible. I'll add a copy-to-task feature later.	15 years ago
Emiliano Heyns	42ad1112eb	Workaround for subissues not updating estimated_hours correctly on their parent ... Only fixes estimated time when the last sub-issue is removed. Workaround until Redmine #5524 is fixed	15 years ago
friflaj	79d1b956ad	Don't count stories without points	15 years ago
Mark Maglana	c0338a9a4d	Fixing a borked merge	15 years ago
friflaj	1c64e99b1a	Rails does array mapping for queries automatically	15 years ago
friflaj	7ba8fcc4e2	wiki page import	15 years ago
friflaj	6dce56cb31	skip wiki page if just checking import	15 years ago
friflaj	e5044d0605	Velocity calcuations	15 years ago
friflaj	a39a569f65	Velocity calculation based on last 5 sprints	15 years ago
friflaj	bab7d6d09f	Wiki page importing	15 years ago
friflaj	077e4e8264	Import wiki pages if available	15 years ago
friflaj	9c38b0ad64	Select product backlog	15 years ago
Mark Maglana	eb30a35ab9	Remove unecessary string conversion of array ... This conversion is not necessary and results in an exception being thrown when using PostgreSQL	15 years ago
friflaj	ff56c5d3fd	Automatically show and sort parent	15 years ago
friflaj	3d219e1713	moved sample project to task dir	15 years ago
friflaj	20475449b6	project import task, burndown generate task	15 years ago
friflaj	c4f89949f7	Journalize attribute updates	15 years ago
friflaj	bd8b4bf5d5	Configurable burnup/down	15 years ago
friflaj	409b74eef5	When an issue is copied, it's most likely the source issue is ... considered a duplicate for the new issue.	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	77a1aada95	multi-tracker story designation	15 years ago
friflaj	6a55d325f4	add backlogs custom filters	15 years ago
friflaj	fa5364754d	Multiple story trackers, fix for #233	15 years ago
friflaj	1958e8866a	migration failed when the plugin wasn't already configured	15 years ago
friflaj	765cd39013	task follows story	15 years ago
friflaj	59e29cc43a	automatically set story descendants to the task tracker	15 years ago
friflaj	bbc50decbb	jquery no-conflict, automatic story link on copy	15 years ago
friflaj	1c35713929	Add "edit wiki page" to version screen	15 years ago
friflaj	96a1a1dcc8	Edit remaining_time	15 years ago
friflaj	01a4f1f1d5	add story-points column to the issue display	15 years ago
friflaj	64e468d50b	Story point editing	15 years ago
friflaj	211dd05e67	Issues sidebar works	15 years ago
friflaj	1f6764a016	Initial checkin	15 years ago
Mark Maglana	b4ba1b3c92	Implement the removal of Backlog and Item	15 years ago
Mark Maglana	5670fb27ff	Remove extraeneous require	15 years ago