Skip to content

Issue Management Rules

mervegrbz edited this page Mar 4, 2023 · 1 revision

Issues are a compelling way of coordinating teamwork. They also help you keep track of what’s happening on projects and provide a durable, replicable record of the work.

Creating an issue

  • Issue title should be descriptive
  • Issue should have clear description
    • State the goal
    • Be explicit about the deliverables
    • Link the other related issues if there is
  • Issue should have at least one label
  • Issue should have a revisor, who will revise and approve before the deadline
  • Issue should have a due date
  • Issue should have a assignee, If there is not issue creator is responsible for assigning the issue.

Working on a issue

  • An issue may take several days, assignee may comment the progress, so that team can know the status
  • Assignee should change the related label while working

Concluding an issue

  • Revisor should be notified before closing the issue, by comments
  • Issue should not be closed before revisor approval

Group 2 Disaster Response Platform

CMPE451

📌 Communication Plan
📌 Docker and local deployment tutorial
📌 RAM
📌 Test Traceability Matrix

📜 Rules
📝 Lab Reports
📅 Meetings
📅 Backend Team Meetings
📅 Mobile Team Meetings
👥 Team Members

CMPE352

📌 Milestone Report 1

📌 Milestone Report 2

📅 Meetings
👥 Team Members
📁 Project
🔍 Research
📜 Rules
📝 Templates
💬 Interviews
Clone this wiki locally