GitLab

Created by: jwillenbring

@maherou @bartlettroscoe @trilinos/framework

We need to implement a project-wide issue management system. It must work for both development-funded efforts, which are being required to apply more rigor to their issue tracking efforts, and for research-funded efforts, which will have more flexibility in use of the issue tracker. The system should have the following characteristics:

Usable: The system should not impose a heavy burden on Trilinos developers. Developers are familiar with a basic issue tracking system, and generally comfortable with using one. The extra requirements for the system should not require large additional time investments. For example, when filing or accepting a ticket, applying labels, estimating effort, assigning, etc shouldn't take more than a few extra minutes.

Well-defined: The process should be documented. Because of the traceability requirement listed below, it is important that certain parts of the process be followed carefully.

Traceable: A primary objective of the new issue management system is that customer requirements be traceable all the way to implementation and delivery. Requirements should be translated into specific issues in an epic-story-task hierarchy to support this traceability for large deliverables.

Visible: Current status should be easily visible for stakeholders, including customers, users, developers, and management.