Backlog

QA creates an issue with 'Bug' type.

Developer receives notification and links a Git branch to the issue.

Developer pushes a commit with the issue key in the message.

Backlog automatically transitions the status to 'Resolved'.

QA verifies and closes the issue.

Product Manager creates Milestones for quarterly goals.

Team creates issues and assigns them to specific Milestones.

PM uses the Gantt chart view to check for resource overlaps.

Developers update daily progress.

Burndown charts track velocity against the Milestone deadline.

Invite client as a 'Viewer' to a specific project.

Client monitors Gantt charts for timeline updates.

Client adds comments to specific 'Task' issues for feedback.

Team responds within the thread, keeping all communication centralized.

Client approves completion via status change.

Technical lead creates a Wiki page for 'API Setup'.

Team members contribute via Markdown editor.

System tracks version history to prevent data loss.

New hires use the Wiki for self-paced onboarding.

Wiki pages are linked directly within relevant issues.

Configure Webhooks to trigger on issue updates.

Jenkins/GitHub Actions receives the webhook.

Automated build starts based on the linked Git branch.

Build results are posted back to the Backlog issue comment via API.

Issue status updates based on build success or failure.

Managers view the 'User' dashboard to see task counts across all projects.

Identify bottlenecks where one developer has high 'Open' task volume.

Reassign parent issues to underutilized team members.

Monitor the change in the collective Gantt view.

Verify load balance in weekly sync.

Create custom fields for 'Part Number' and 'Hardware Revision'.

Use 'Task' for physical assembly and 'Git' for firmware.

Link firmware commits to the specific hardware revision issue.

Track lead times using the start/end date fields.

Export project data for supply chain audits.