Webdev/Web Production/Kanban: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 128: Line 128:
<p>Bugzilla is used by everyone at Mozilla and our community. We want to keep our projects and tasks open. We also need to have a single
<p>Bugzilla is used by everyone at Mozilla and our community. We want to keep our projects and tasks open. We also need to have a single
source of truth for information about a task. For these tasks Kanban is the "when", Bugzilla is the "what".</p>
source of truth for information about a task. For these tasks Kanban is the "when", Bugzilla is the "what".</p>
<p>Kanbanery does have an issues tab, however we recommend that you do not use this for either storing the primary bug or any sub-tasks (more below).</p>


<h3>Priority</h3>
<h3>Priority</h3>
Line 140: Line 141:


<p>A powerful feature of Kanbanery is that cards can consist of multiple tasks. These will often have corresponding bugs in Bugzilla. The format
<p>A powerful feature of Kanbanery is that cards can consist of multiple tasks. These will often have corresponding bugs in Bugzilla. The format
for sub-tasks should be "Description #BUGID" when appropriate. We suggest you do not use the kanbanery issues tab for storing either the primary bug or sub-task bugs.</p>
for sub-tasks should be "Description #BUGID" when appropriate. </p>


<h3>Deadline</h3>
<h3>Deadline</h3>
canmove, Confirmed users
2,745

edits

Navigation menu