Project Management: Boards, Sprints & Issues
How projects, boards, issues and sprints fit together — and who gets to see a project at all.
Project Management is where you organize and track work that has a clear start, an end, and a team working on it together.
What Project Management does here
Work is tracked as projects. Each project is broken down onto a board, and — if you want extra structure — issues within a project can optionally be grouped into time-boxed sprints.
Projects & boards
Every project has its own kanban-style board: a visual layout of columns you define yourself. A simple setup might be To Do, In Progress, and Done, but the columns are yours to customize to match how your team actually works.
Screenshot goes here
A project board with customizable columns
Issues
An issue is the actual unit of work — a task or piece of work to be done. Issues are created, assigned to someone, and moved across the board as they progress from one column to the next. Anyone involved can comment on an issue, so discussion about the work stays attached to it.
Screenshot goes here
An issue showing its assignee and comments
Sprints
If you want to plan work in time-boxed chunks, issues can optionally be grouped into a sprint — a defined period during which a set of issues is planned to be completed. Not every project has to use sprints; it's there for teams that want that extra layer of planning.
Who can access a project
A project has its own membership list, separate from broader role permissions. People are added to a project as an owner, a member, or a viewer, and only people on that list can see or work on the project at all. Having a general role in VroduxERP isn't enough on its own — someone also needs to actually be added to a specific project before they can access it.
Screenshot goes here
A project's membership list showing owner, member, and viewer roles
Where to go deeper
- Managing project membership → — adding and removing people from a project, and changing their role