Repository navigation
1 Issue Tracking
Following the “Issue Tracking” policy with bidirectional tracking. Developers should apply this rule in all commits made to the project.
Issue Tracking, also known as issue tracking or issue control, is a process used to record, manage, and track issues or problems that arise during the development of a software project or in other areas of work. These issues can include bugs, feature requests, enhancements, tasks, and any other form of issue or task to be addressed.
The main purpose of Issue Tracking is to provide a structured way to organize and prioritize issues, allowing the team responsible for the project to track them efficiently. This helps ensure that no issues are overlooked or overlooked, and that the necessary actions are taken to resolve them.
Issue Tracking also allows for communication between team members as it is possible to add comments, notifications and updates on the status of a specific issue. This promotes collaboration and information sharing, making it easier for teams to work together to solve problems effectively.
1- When committing, put the same Issue number, using the formatting from step 2.
2- Put the Issue number, colon, space and description of the commit.
All Issues generate an ID, which will be linked to a User Storie, which will refer to the Epic, following the bidirectional tracking pattern.
Assigning IDs to each commit helps track and uniquely identify each work item in the project. This enables better visibility and understanding of the status of tasks, facilitating communication between team members.