Activity log for bug #496534

Date Who What changed Old value New value Message
2009-12-14 14:11:03 Daniel Kulesz bug added bug
2009-12-14 14:22:36 Daniel Kulesz description Currently, the Review protocol implemented is quite *too* verbose, this is, it needs to many pages to present the relevant information. It uses a table for each Finding, and repeats the following information too many times: - the word "finding" before the finding's number - date and time for the session (a table with all sessions would be sufficient, the number could be just referred) - the word "severity" before each severity etc. Another concern: I think, most organizations might already have a review template, that is already in use since several years (if we assume they DO reviews actually). Therefore the least intrusive way to introduce RevAger into such an organization would be to re-use those templates. To address these concerns, I propose to re-write some parts of the Protocol export functionality in order to make it template-based. I suggest we should use some format that allows for filling text marks - maybe RTF? Does it support that? (I am pretty sure at least OpenDocument does that, but RTF is more compatible) Currently, the Review protocol implemented is quite *too* verbose, that is, it needs too many pages to present the relevant information. It uses a table for each Finding, and repeats the following information too many times: - the word "finding" before the finding's number - date and time for the session (a table with all sessions would be sufficient, the number could be just referred) - the word "severity" before each severity etc. Another concern: I think, most organizations might already have a review template, that is already in use since several years (if we assume they DO reviews actually). Therefore the least intrusive way to introduce RevAger into such an organization would be to re-use those templates. To address these concerns, I propose to re-write some parts of the Protocol export functionality in order to make it template-based. I suggest we should use some format that allows for filling text marks - maybe RTF? Does it support that? (I am pretty sure at least OpenDocument does that, but RTF is more compatible)
2010-01-15 15:24:24 Holger Röder summary (FR) Simplify protocol / Offer user-customizeable protocol templates (FR) Simplify protocol
2010-01-15 15:29:26 Holger Röder revager: milestone 1.3rc1
2010-01-15 15:29:31 Holger Röder revager: importance Undecided Medium
2010-01-18 11:51:54 Daniel Kulesz nominated for series revager/1.4
2010-01-18 11:51:54 Daniel Kulesz bug task added revager/1.4
2010-01-21 02:57:32 Johannes Wettinger revager: milestone 1.3rc1
2010-04-29 17:14:05 Johannes Wettinger revager/1.4: importance Undecided Medium
2010-04-29 20:01:18 Johannes Wettinger revager: importance Medium Undecided
2010-04-29 20:01:20 Johannes Wettinger revager/1.4: importance Medium Undecided
2011-01-11 14:26:10 Johannes Wettinger tags feature-request protocol 2.0 feature-request protocol