My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 752: Enable "agile" prioritization of changes
2 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Reported by gregory....@gmail.com, Oct 11, 2010
Changes prioritization could be a very nice feature. It would help to plan reviews.

Priority must not be a property such as "low, high..." but an order; the change with the unique priority "1" must be treated before the change with the unique priority "2".

Ideally, prioritization should be done by drag & drop in the web interface.
Dec 13, 2010
Project Member #1 fredrik....@sonyericsson.com
The word "must" makes me associate to "mandatory" and "enforced".
Is it your intention to force the reviewer to review changes in a certain order? Who did you have in mind to do the sorting of the issues?
Dec 13, 2010
#2 gregory....@gmail.com
In my team we need to prioritize the reviews depending on their interest and their cost (effort). Sorting is done by the project team.
Sign in to add a comment

Powered by Google Project Hosting