67 Commits (784f2537b5c44b9cc728d78de5d1c3dcddf08cf4)

Author	SHA1	Message	Date
friflaj	79baa96dbd	sample burndown chart	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
Mark Maglana	8cac265f83	Add front-end functionality for editing stories	15 years ago
Mark Maglana	bb7a5699e9	Update version information	15 years ago
friflaj	ce9e2dbf3a	plugin info updated	15 years ago
Mark Maglana	67a3afb266	Various implementations have been made to integrate the ... changes in 2.x to 2.1. Highlights are: * Javascript has been removed from views to their own files to make them unobtrusive and, hopefully, easier to manage down the line * Server-side variables used by js files are shared via a dynamically generated js file (jsvariables.js.erb) * Partials for backlogs and stories have been created in preparation for when #50 (Real-time updates) is implemented * Methods/functions that are used to generate presentation strings have been moved to helpers * The layout has been changed to make use of the entire browser estate * The drag handle for each story has been removed as they are now unecessary: When a story is dragged, it is smart enough to not enter the editing phase. Only when clicked will it become editable	15 years ago
friflaj	fa5364754d	Multiple story trackers, fix for #233	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	aa56238678	Storypoint recalc on drag-drop, auto-create sprint wiki link	15 years ago
friflaj	43c2def99b	Story point editing	15 years ago
friflaj	211dd05e67	Issues sidebar works	15 years ago
friflaj	1f6764a016	Initial checkin	15 years ago
Mark Maglana	a97c5c4a75	* Do a proper authorization check in controllers ... Controllers didn't do a proper authorization check prior to this. This fixes that security hole. In the future, a more fine-grained set of permissions will be made available. For now, it's all or nothing.	15 years ago
Mark Maglana	217d2c42b0	- First import into new repo	15 years ago