The requirements register

A requirements register is a list of what a company is obliged to do: the norm each duty comes from, the obligation in your own words, who answers for it, what proves it and when it is next reviewed. Here it is a project set up for that in one action, instead of an hour with five settings screens.

It is the one ready-made project today. What you take becomes your project’s own — its columns, its type, its pages — and is changed afterwards like anything else; nothing keeps pointing back at a pattern.

With the samples box ticked it also files five sample requirements and three sample pages about an invented payment company. They cite real acts, are labelled sample, and each ends with a line saying it is a sample and not advice.

• When you create a company or a project. The form asks Start with and offers Empty board or Requirements register. Chosen there, the register arrives with its samples.
• In a project that exists. Board menu → Ready-made project…. The sheet says what it would bring; tick the samples if you want them and press Take it. Afterwards it lists what was added and what was left.
• Through MCP. list_project_presets says what it would bring, and take_project_preset takes it — with samples: true for the samples.

Anybody on the project can open the sheet and read it. Taking it is for the project’s lead, a board administrator, the company’s owner or an admin.

Only what the project lacks is added, and everything is matched by name: a column, a type, a recurring issue or a page of the same name is left as it is. So it can be taken into a project that already holds work, and taking it twice adds nothing.

The workflow is the exception. It is taken only by a project with no issues that still has the states it was created with — replacing a workflow means saying where each state’s issues go, and this action does not ask. Otherwise it is left, and the same workflow is offered in the board menu under States & transitions….

Nothing starts by itself. The recurring issues arrive switched off; samples are filed only when asked for.

• Columns — rename, add or remove under board menu → Fields…. The answers of Compliance are a list you can change.
• States — board menu → States & transitions….
• Recurring issues — board menu → Recurring issues…: read each, change its day, its assignee and its words, and switch on the ones that are yours.
• Reminders — board menu → Due-day reminders….
• Page templates — they are ordinary wiki pages. Edit them; or mark a page of your own with Make a template, and it is offered under From a template when a page is made in that wiki.
• The samples — find the issues by the label sample and the pages by titles that begin «Sample:», and delete them once you have looked.

The register is read as a table: the table view shows a row per requirement with your columns in your order, grouped by state or by Compliance, and Export downloads it as one .xlsx. A guide walks through it: A requirements register in half an hour.

A project is imported from a cloud site of the compatible tracker in Settings → Import, by a company administrator: the site’s address, an account’s email and an API token. Nothing is written until you have seen the plan and pressed start. Issue keys stay; issues, comments, files, custom fields and versions are carried; change history, sprints, logged time, watchers and components are not.

Take the register into the imported project afterwards: it adds only what is missing, so your own columns stay and the register’s arrive beside them. The workflow will be left as it is, because the project holds issues.

Wiki pages have no importer. The wiki answers the compatible wiki’s API (the wiki API), so a tool that writes pages there writes them here; otherwise a policy is pasted in as Markdown.

• No second ready-made project yet, and no way to save a project of your own as one.
• A column cannot point at an issue or a wiki page: Evidence and How we meet it are text.
• No risk column and no row number; the issue key is the number.
• The register’s words exist in English and Russian. In another language of the product they arrive in English.
• No removal of the samples in one action.
• A recurring issue does not fill the register’s columns.
• The samples and the recurring issues are examples with their sources, not a statement of what applies to you, and not legal advice.