Skip to content

Issue Tracking

Jordan Padams edited this page Mar 15, 2021 · 11 revisions

Issue Tracking

Getting Started with Zenhub

Go to the applicable board to view / create / update new tickets:

Alternatively, you can install the Zenhub Chrome/Firefox extension to view Zenhub within Github:

Issue Creation Best Practices

The PDS has uses the article “Naming Guide For Task, Bug, and User Story Titles” for issue best practices.

Here are some high-priority best practices we really want to try to follow:

  • In general, for tasks, bugs, and new features, at minimum, start the title with a verb (e.g. Ingest some data from somewhere or Update this page with some change)

  • Title should be able to tell someone what was fixed or completed

    • We plan on using these issue titles for generating changelogs and report automatically
  • Use autolinked references wherever possible for traceability

    • Using references is a HUGE benefit in streamlining productivity, project management, provenance, and requirements/test traceability.

Bug Prioritization Policy

PDS follows a bug/defect prioritization policy that is similar to that used by flight projects, with a twist for the needs of issue tracking.

Consequence
1 2 3 4 5
5 LOW MEDIUM HIGH CRITICAL CRITICAL
4 LOW MEDIUM HIGH HIGH CRITICAL
Likelihood 3 LOW MEDIUM MEDIUM HIGH HIGH
2 LOW LOW LOW MEDIUM MEDIUM
1 LOW LOW LOW LOW MEDIUM
Level Description Consequence Definitions
5 Very High Mission Failure
4 High Significant reduction in mission return
3 Moderate Moderate reduction in mission return
2 Low Small reduction in mission return
1 Very low Minimal reduction in mission return
Level Description Level Definition Percentage (%)
5 Very High Almost certain 70% < X ≤ 100%
4 High More likely than not 50% < X ≤ 70%
3 Moderate Significant likelihood 10% < X ≤ 50%
2 Low Unlikely 1% < X ≤ 10%
1 Very Low Very unlikely X ≤ 1%

Help with Zenhub

We use Zenhub to visualize all our tickets across Github.com repositories.

References