search

lindsaykh / act_project

MIT License
3 stars 0 forks source link

EXAMPLE ISSUE #3

Open C-Miranda opened 1 year ago

C-Miranda commented 1 year ago

Metadata Field Definitions

  1. Assignees: Check the box next to the name(s) of team members who will work on the issue.

  2. Labels: Select label that applies to issue.

  3. Milestone: Select relevant milestone. We will use milestones as our epics. Milestones are used to group and track issues and pull requests. You can add a new milestone to any task by navigating to the "issues" tab, and clicking "Milestones" and then "New Milestone", once a milestone is added, it will show up as an option for selection.

  4. Status: Only move assigned tasks into "To-Do", "Test" or "Done". Unassigned tasks should remain in "No Status".

  5. Linked Pull Requests: Description TBA

  6. Priority: Refer to the Priority Table below.

  7. Department: Department names match the names of folders in the master for Google Drive.

  8. Boundaries:

    • Client-side is an application that runs at the users' computer. It could be a stand-alone application (more often) or it could refer to a web browser based interface (less likely).
    • Frontend also faces the end-user and generally runs in a web browser based interface. I haven't heard of thick clients being referred to as a front-end.
    • Backend refers to processes and services that are running either on another server or in the background of the users' computer. More often than not, it refers to processes that are not on the end users' computer. But the key, as you mentioned, is that the end user is not necessarily aware of the processes running.
    • Server-side is an extension of back-end but explicitly reinforces the fact that the processes are running somewhere else and not on the end users' computers.

  9. Documentation: Description TBA

  10. Repository: Should always be "act_project".

C-Miranda commented 1 year ago

PRIORITY TABLE

Please use the following table when assigning a priority to an issue.

  1. Immediate: The requirement is critical to the project’s success. The project will not be possible without fulfilling this requirement.
  2. High: The requirement is high priority, but project can still be implemented in a MVP framework.
  3. Moderate: The requirement provides value and will greatly improve the project’s success, but the project could still be implemented in a MVP scenario
  4. Low: Project success does not depend upon it
  5. Prospective: Requirement is out of project scope and is included as a possible component of a prospective release/feature.