ptc-catalog

Evaluate and Use an Issue Tracker

Download this PTC (Markdown)

Target

Identify an issue tracking system which fits the team’s needs.

User Story

As a software developer, I want to keep track of bugs and user feature requests so that I can keep track of and prioritize the work the team decides to tackle (or not).

Card

  1. No formal issue/bug/feature request tracker in place.
  2. A requirements list for the potential issue tracker has been created. Developer use cases / workflow have been identified and documented for potential issue tracker candidates at this stage.
  3. A list of potential issue tracking tools has been generated based on research and evaluation of features, cost, etc.*
  4. Team has executed time-boxed plan and actively uses the issue tracking tool as per the plan in place on a trial basis.
  5. Full adoption of issue tracking system by all members of team. Examples of adoption include active use of issue tracking tool to include the migration of existing bugs/feature requests and creation of new bugs/feature requests into the new system.
  6. Documentation developed by team on prioritization process and use of issue tracking tool so that new user request can be correctly created by new team members, etc.

Comments

*The development team may decide that a formal issue tracker is not needed based on this research and evaluation.


Thanks @prwolfe @jeanshuler for the help!

Acknowledgement

This Project Tracking Card originated from the PSIP PTC Catalog. The development of the PSIP PTC Catalog was supported by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration.