Record fields

The tables describe the standard fields of the main records. The administrator can add their own fields to them: “Custom fields”. Which fields you see and can change is determined by the role's permissions.

Task

Field	Meaning	Format	Where it is filled in
Title	A brief description of the work	Text, required	The “New task” form, the card
Description	Details, completion criteria	Text with formatting	The form, the card (autosave)
Type	The card kind. Defines the workflow	Choice from task types	The form. Change: the card, the pencil at the type
Project	The project the task belongs to	Choice	Determined by where it is created
Assignee	Who performs it	A project team member	The form, the card, tables
Release	The task's release or “No release”	Choice among unfinished releases	The form, the card
Group	A project group label	Choice	The card
Start	The date work starts	Calendar day	The card
End	The deadline	Calendar day	The card
Estimate	The planned time	Hours/minutes, format 1.5, 1d 2h 30m, 90	The form, the card
Spent	The sum of logged hours	Read-only	Calculated from tracks
Number	A key like RGM-30	Read-only	Assigned on creation
Tags	Labels	Up to 50 project tags	The form, the card
Parent task	For subtasks	Choice of the same scope (project and release)	The form, the “plus” icon in the table
Stage	The process step	Only by a transition	The “Stage” block, the board

Project

Field	Meaning	Format	Where it is filled in
Client	The customer	Text, required	The “New project” form, the overview
Product	The customer's product	Text, required	The form, the overview
Name	The project name	Text, required	The form, the overview
Prefix	A code for task keys	A–Z, 0–9, hyphen, up to 10 characters, unique	The form, the overview
Description	The project description	Text with formatting	The form, the overview
Project type	The kind of project	Choice from a directory	The form
Release type (workflow)	Allowed release processes	Several values, at least one	The form, settings
Task types in new releases	Types allowed in releases	Several values, at least one	The form, settings
Owner	Responsible for the project	A user	On creation — you
Team	Members and role labels	A list	The form, settings
Area of responsibility	A description of a member's duties	Text	Settings
Folder	The place in the project list	Choice	The project list
Project tags	A directory of colored tags	A directory	Project settings, “Manage tags”
Kickoff meeting date	The start of the delivery cycle	Date	The overview (at the “Kickoff meeting” stage)
Meeting outcome	The result of the kickoff meeting	Text	The overview
Proposal files	Commercial proposal files	Files, limited in number	The overview
Proposal agreement date, Agreed amount	Proposal agreement	Date, amount	The overview
Contract, Release plan, Scope of work, Dates	Development entry data	File, text	The overview
Delivery date, Acceptance date, Closing amount, Act / Invoice, Completion date, Project results, Closing documents	Closing data	Dates, amount, files, text	The overview
Support type, Budget limit, Pricing model, Support contract, Support end date	Support project data	Text, number, file, date	The overview

Which of these blocks are shown on the “Overview” page depends on the project stage and on block visibility settings.

Release

Field	Meaning	Format	Where it is filled in
Name	The release name	Text, required	The form, the overview
Project	The release's project	Choice, required	The form
Type	The release type (SCRUM, KANBAN, SUPPORT…)	Read-only after creation	Determined by the project
Assignee	Who is responsible for the release	A user	The form, the overview
Estimate	Planned hours	Hours. An automatic sum over tasks if not set manually	The form, the overview
Start date, End date	The release period	Calendar days, required	The form
Target date (planned)	The delivery date	Date	The overview
Task types in this release	Allowed types	Several values	The form, the overview
Description	The release description	Text with formatting	The form, the overview
Actual composition	What went into the release	Text	The overview
Readiness date	When the release is ready	Date. Filled in automatically on the transition to “Ready for delivery”	The overview
Handover date	When the release was handed over	Date	The overview
Client acceptance date	When the client accepted	Date	The overview
Internal checklist, Handover materials, Act / invoice	Files	Files	The overview
Closing amount	The closing amount	Number	The overview
Spent	The sum of hours over tasks	Read-only	Calculated from tracks

Track (a time entry)

Field	Meaning	Format
Task	The task the time is logged on	Choice, required
Work type	The kind of activity	Choice, required
User	Whose time it is	You by default
Start	When work started	Date and time
End	When it ended	Date and time, not in the future
Duration	How long the work lasted	1.5, 1d 2h 30m, 90; from 1 minute
Description	What was done	Text, required

Any two fields of three are filled in: start, end, duration.

User

Field	Meaning	Format
Email	The address from Keycloak	Must match Keycloak. Not changed in the profile
Username	The user name	2–64 characters: Latin letters, digits, ., _, -
Last name, First name, Patronymic	Full name	Text
Phone	The phone	Text up to 32 characters
Role	A set of permissions	Choice
Status	Active / Disabled	By a transition
Rate type, Hourly cost	For calculations	Hourly or fixed, a number. Available to roles with the rate permission
Time zone	Defines the days of tracks	IANA, for example Europe/Moscow. If not set, Asia/Bangkok