Huly Project Management

Huly handles duplex communication for issue creation, update and closure with Github, however as a general rule:

Issue Creation & Management

Every new feature, improvement, or bug is logged as an issue in Huly.
Issues must include:
- A clear title and description.
- Relevant labels (e.g., bug, feature, enhancement).
- An individual assignee.
- An estimated priority and due date, if applicable.

Backlog: New tasks enter the backlog.
In Progress:
- When a developer starts a task, they must update its status to “In Progress.”
- This status indicates active work and should be visible on the Kanban board.
Code Review/QA:
- Once work is complete and a PR is opened, the task status can move to the project's “Under Review” column.
Done:
- After successful code merge and QA sign-off, the task is marked as “Done.”
Collected:
- Upon financial closure, the task is marked as "Collected."

Reference the Huly issue ID in commit messages and PR descriptions for traceability.

Check out this video for more on Huly!