$if(R.q!="") $(items=db.Search(R.q))
$end $if(R.id==ritem.uid) $end $(i=0) $(items=db.SidebarItems(R.id)) $for(item,items) $(i=1) $end

$fa.TypeIcon2(item[0].y,"sm")

$item[0].x1

$if(i==1)
$end

$if(editable)

•   Document
•   Object
•   Action
•   Event
•   Import
•   Import pack

    $if(R.id!="1")     $end $end

Tags

A tag is a word on an item. Most of them mean only what they say — they are there so you can find things and so a report can group them. A few change how KF behaves, and those are not offered in the tag picker.

Tags are declared per item class in .conf/config.ogdl, each with the job it does:

Job	What it means
status	The item's state. SetStatus owns these and they are mutually exclusive.
mark	Descriptive. Means what it says and nothing else.
report	A report or a table reads it by name.
nav	System. Changes whether and where the item appears in the interface.
structure	System. Changes inheritance or the structural rules.

Status

Three tags, and they are exclusive: setting one clears the others. A fourth state, pending, is the absence of all three, and missing is derived and never stored.

Tag	Meaning
done	Somebody marked it done. Not the same as the requirement being met — the evidence still has to be read.
resolved	Answered at type level, on every instance's behalf. Everything nested under it is hidden from instance lists.
not_applicable	Declared not applicable. A justification should exist; ask for it.

Objects

Tag	Meaning
situation	The item describes a situation or context rather than a thing.

Events

Events carry their own lifecycle words, and a cause classification.

Tag	Meaning
open	The event is still being worked on.
closed	The event is finished with.
pending	Waiting on somebody or something.
happened	It actually occurred, as opposed to being a potential failure mode. Shown with a warning icon.
discarded	Considered and set aside. Shown with a cross.
root_cause	This event is the root of the chain, not a link in it.
malfunction	A functional failure, as distinct from a hazard.
hazard	A source of harm, in the ISO 26262 sense.
hazardous_event	A hazard in an operational situation — a hazard plus a situation.

The six Ishikawa cause categories, for grouping causes in a fishbone:

man, machine, material, method, measurement, environment.

Actions

Tag	Meaning
function	The action states a function the item performs.
solution	The action is the answer to a problem. Shown with a tick.
change	A design change. What DRBFM reviews.
test	A test. What DRBTR reviews.
verification	Verification activity.
preventive	Prevents the failure rather than catching it.
containment	Contains the effect rather than removing the cause.
passed	The test or check passed.
failed	The test or check failed.
accepted	The result was accepted.
rejected	The result was rejected.
good	A good outcome. Shown with a thumb up.
bad	A bad outcome. Shown with a thumb down.
noEffect	The action had no measurable effect.
root_cause	The action addresses the root cause.

Four that a report reads by name:

Tag	Read by
requirement	The compliance register and the requirements report.
rule	The requirements report.
safety_goal	The ISO 26262 safety goal report.
safe_state	The ISO 26262 safe state report.
milestone	The Gantt, which draws it as a milestone rather than a bar.

Signatures and roles

Signatures: accept, reject, comment.

Roles: responsible, editor, reviewer, team-leader, technical-leader,

team-member.

System tags

These four are not offered in the tag picker, because setting one because it sounds descriptive changes how the database behaves. They remain writable through the REST API and through config.ogdl, where whoever sets them has had to find out what they do. An item that already carries one keeps it: the picker shows it, selected, so that saving the item does not strip it.

Tag	Job	What it actually does
reference	structure	The big one. Type traversals stop at a reference item, it is exempt from the rule that an item has one parent, and Clone never copies it. This is what lets one quality manual be the evidence for twenty requirements without twenty copies of it — and it is why setting it casually changes inheritance across the database.
topmenu	nav	Puts the item in the top navigation bar of every page.
class	nav	Suppresses the item's tab bar and action bar. Used for structural containers like Products and Processes, which are places rather than records.
no_menu	nav	The same, for documents.