Confirmed users
28
edits
(Comment that priorities & severity must be made clear even if the bug is unassigned.) |
(Unassigned bugs may never be resolved.) |
||
Line 27: | Line 27: | ||
>><big>''Does this increase the risk of a bug not being addressed in due time?''</big> - [roland] only low priority bugs; We don't have the resources to care about low priority bugs, if we had the people we could care about all bugs but that'll never happen in Mozilla :-) | >><big>''Does this increase the risk of a bug not being addressed in due time?''</big> - [roland] only low priority bugs; We don't have the resources to care about low priority bugs, if we had the people we could care about all bugs but that'll never happen in Mozilla :-) | ||
* '''Don't''' worry if low priority bugs remain unassigned; this leaves bugs for volunteers and new folks to tackle | * '''Don't''' worry if low priority bugs remain unassigned; this leaves bugs for volunteers and new folks to tackle | ||
: >> [J99] '''But many other bugs get in the same unasigned bucket. It means important bugs do not get fixed''' | |||
::* Volunteers and new folks | |||
::** Are not Lithium Admins so can not make changes to Sumo Lithium | |||
::** Are not able to file or see Lithium Cases | |||
::** High priority and sever bugs will remain unfixed. <br /> Redirects and related showfor bugs, documentation etc issues have been around for the three months since the migration, and in many cases were identified as likely issues in or prior to the beta testing. | |||
::** Even if bugs are assigned and high priority recent experience indicates they still may not be actioned & resolved quickly, but if they are assigned it is up to the module owner and asignee to follow up and Bugzilla is at least enabling us to see & manage the situation. [[User:John99|John99]] ([[User talk:John99|talk]]) 04:06, 14 May 2017 (PDT) | |||
= Lithium specific stuff = | = Lithium specific stuff = |