On 12/07/2012 09:01 AM, Lydia Pintscher wrote:
No I think we're talking past each other a bit ;-) Assigned means we (the Wikidata dev team) picked up the bug/task for the current sprint. It is not always immediately clear who is going to work on the bug during the sprint. It is just clear that we intend to work on it. This decision is made in a meeting of the whole team. At the end of the meeting someone goes and changes the bug status accordingly for all of them. During the sprint developers pick from that list as they wish/have the skills.
Then those ASSIGNED bugs are not really assigned. By setting as ASSIGNED nobody else will attempt to fix them, but then again perhaps nobod is working on them and nobody will actally have the time to work on them on the current sprint, being postponed when perhaps someone else would have taken them.
A more accurate approach would be to set those bugs to "Highest" priority in order to identify them for the current sprint. This is less than "Immediate" (something requiring immediate action) and more than "High" (something important, perhaps for the next sprint).