Go to Bugzilla - So we can go to Bugzilla and do the rest of the markup that this UI can not do.This means there are component container tiles with some "+" button for adding bugs. Making dependent bugs - This is the most important because it is most like the Notepad tracking the ability to make new bugs quickly in a component.Once this is available, the rest of the project can proceed. The biggest complication I see is finding/making a library that will be responsible for drawing, moving, and saving these tiles. I imagine this implemented as a React/JSX app. A button to click to show new-bug defaults (component, tags, blockers, etc).A button to click to show Bugzilla list.A way to show all open bugs that match container's criterion.A way to hide bugs that match criterion.Large region that contains the bugs which match container's criterion.I would imagine the bottom of the screen will have a radio button of all the container tiles so they can be selected-and-viewed.Ĭontainers have decoration that is different than bugs Since each of these properties can vary independently, only one can be shown at a time. New-InProgress-Complete - A typical 3-part kanban tracking container.Dependencies - As mentioned above, we can view the dependency tree of bugs as tiles-in-tiles.Whiteboard tag - Containers that represent bugs with a particular whiteboard tag.Product::Component - Containers that bugs can be moved between to control component they are in (or to make new bug in).There will be other tiles, containers really, that will represent a variety of bug states. A region to drag blocker bugs into (at which point the bug is now a container).A region to hover to see the bug summary.A button to click to add a blocker bug - Assumed to be in same component.Dependent bugs - A bug with dependencies will expand to hold.An "X" to close the bug, and a way to reverse that decision (?ctrl-Z?).Each bug is represented as tile with the bug's short description. Not sure if formatted correctly - WYSIWYG comments would be nice.I want a shortlist of what I am working on. Hard to search - There are too many bugs I am not interested in.Lots of scrolling - the ui complexity forces user to scroll, slowing down data entry. Visually complex - There are multiple fields I never use, or always have the same value entered.Long page load times - a few seconds to load/save a page breaks the flow of prose in my head.Using a bug tracker, like Bugzilla, is good for team communication but like all communication, it has costs: Tracking bugs this way has low administrative cost, and a high bug density. I like to track my work in a Notepad, with each line representing a TODO item. Nevertheless, Bugzilla maintainers notified all affected users and advised them to change any similar passwords they may have, he said.Manage Bugzilla bugs as tiles with short notes Problem Since the database originated from a development server that was used to test potentially insecure Bugzilla builds, many users likely had passwords for their accounts that were not reused elsewhere, Côté said. "As soon as we became aware, the database dump files were removed from the server immediately, and we've modified the testing process to not require database dumps," Côté said Wednesday in a blog post. The files had been generated during the migration of a testing server for early builds of the bug tracking software, according to Mark Côté, the Bugzilla project's assistant lead. The new data security breach disclosed Wednesday is similar and also resulted from database dump files being left in an unprotected location on a server for around three months beginning May 4th. On August 1, the organization announced that the email addresses of 76,000 users and the encrypted passwords of 4,000 users of the Mozilla Developer Network were exposed for a period of 30 days after a database dump file was stored on a publicly accessible server.
0 Comments
Leave a Reply. |