Treasury contracts

The sprint's developer list feeds planned capacity and the burndown. Joining or leaving in the middle changes the capacity line — the chart starts comparing against a different team.

The "Time (h)" field records how many hours that person dedicates to THIS sprint, not their total workload: someone who splits the week between two fronts enters each sprint with the corresponding slice. It is the sum of these individual times that gives substance to the capacity declared in the sprint record — if the sum of the allocations does not come close to the capacity, one of the two numbers is wrong. Role and note complete the record: what the person does in the round and any caveat (vacation in the middle, part time etc.).

Here you see and fix loose child records, one by one. In day-to-day work, however, the right thing is to create and edit them inside the parent record's form: that is where the business rules run (recalculated totals, validations, numbering, history). Editing directly here is useful for auditing and for correcting a specific case — but it can leave the parent record with an outdated total, and that raises no error on screen.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

In the Sprints record (Operations ▸ Sprints ▸ open the round): the allocated devs are a detail of the sprint itself, maintained inside it — this entry exists to give names and help to the fields of that detail. When building the allocation, record the employee, their role in the round, the time in hours and the status; the note is the place to write down what the numbers do not tell, such as an absence already agreed in the middle of the period.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".