[Development] [QA] Suggestion -- Bug Reports' Assignment

Shaw Andy Andy.Shaw at digia.com
Tue Mar 12 14:41:33 CET 2013

I would expect that the workflow is that if a report is set to be "In progress" then this is the indication that someone is actually working on the report, if we start using the assigner for this indication then it sounds like it will complicate matters even further. Also, if a P1 is created and it is unassigned, who is responsible for ensuring that gets picked up and processed?


From: development-bounces+andy.shaw=digia.com at qt-project.org [mailto:development-bounces+andy.shaw=digia.com at qt-project.org] On Behalf Of Motyka Rafal
Sent: 12. mars 2013 14:28
To: development at qt-project.org
Subject: [Development] [QA] Suggestion -- Bug Reports' Assignment


I want to express another suggestions for bug management:
- A newly opened bug report shouldn't be automatically assigned to anyone.
- Logged-in users should be able to assign bug reports to themselves.

Assigned = 'someone works or is going to work on the item'
Unassigned = 'nobody works on the item'

Please feel free to comment on this.
If there are no serious objections, this change will be introduced soon. The impact of the change will be evaluated.

Best regards,


Rafal Motyka
QE Engineer
Digia, Qt

Email: rafal.motyka at digia.com<mailto:forename.surname at digia.com>
Mobile: +47 95005389
Qt Blog: http://blog.qt.digia.com/
Qt Facebook: www.facebook.com/qt<http://www.facebook.com/qt>
Qt Twitter: www.twitter.com/qtcommercial<http://www.twitter.com/qtcommercial>


This message and any attachments are intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error, please contact the sender immediately and delete the message and any attachments accompanying it. Digia Plc does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130312/10a8798a/attachment.html>

More information about the Development mailing list