Documentation

You create your account, invite the team and open the first project, which automatically gets its own key in the PRJ-142 style. You then configure statuses, priorities, labels and issue types from the lookups, build the backlog and start the first sprint.

Work is organised on four levels: the project, its milestones, the sprints and the tasks. Every task carries a status, a priority, a type and labels, can depend on another one (blocks / blocked by), and collects worklogs, comments and entries in the activity journal. 4myprojects exposes no public API and issues no API keys to customers — you work from the panel.

4myprojects does not connect to Git repositories, chat apps, calendars or automation platforms — there are no external connectors and no data is pushed to third-party services. Instead it keeps in a single place what is usually scattered: the Kanban board, the backlog, the sprints, the Gantt with milestones, the dependencies between tasks, the time logs, the comments and the activity journal. The account is the same one you use across the 4b2b ecosystem, so the team signs in to the panel with the credentials it already has.

The backlog holds everything that is not planned yet; from there you pull tasks into a sprint. The Kanban board shows them by column, with status, priority, type and labels. Closing a sprint leaves you the burndown and the velocity, and whatever was not finished returns to the backlog.

The order that works: set up the project structure and its milestones, configure the lookups (statuses, priorities, labels, types), assign the resources on each project and check the team workload, then plan the first sprint. After the first week of time logging you already have time reports per task and per member.

There is no automatic import: 4myprojects does not pull data from Jira, Asana, Monday or ClickUp, and it does not read CSV files. You rebuild the structure directly in the platform, and in practice that goes fast if you start with the active sprint and the open backlog — the rest of the history can stay in the old tool as an archive.

Administrators learn the lookups and the project structure; project managers work on the backlog, the sprints, the Gantt with milestones and team workload; team members stay in their own work page, where they see their tasks, log time and comment. The easiest way to practise is a test project kept apart from the real ones.

The frontend runs on Next.js, the projects service on FastAPI, and the data lives in PostgreSQL. Everything runs in Docker containers behind a gateway that validates access, on servers inside the European Union.