This guide outlines the operational workflow that every developer in the team must follow.

The goal is to maintain a clear, traceable, and collaborative process, using Jira for task management and Git for version control.

🔑 Core principle: Every code change must be traceable to a specific task. Since the system is modular and extensible, having a clear structure in branches and PRs is essential.

👋 New to Jira or GitHub?

Check our Getting Started with Jira & GitHub and Git Naming & Commit Conventions before continuing.

📌 1. Checking Assigned Tasks

• Each developer is responsible for regularly reviewing their assigned tasks on Jira.
• Tasks initially appear in the "TO-DO" column.
• If the task lacks information or is unclear:
  • Move it to "WAITING FOR INFO"
  • Add a comment in the task specifying what’s missing.

🌿 2. Branch Creation

Every task must be associated with a dedicated branch.

The branch name must include the task ID (e.g., CND-123).

Recommended method:

• Create the branch directly from the task panel in Jira, under the Development section.

Alternatively:

• Create the branch manually using this naming convention: