A risk rule keeps running once you save it. Its state says whether it evaluates now, its owner answers for what it raises, and its row menu lets you pause, hand over or delete it.

Rule states and the row menu #

The State column shows Enabled, Paused, Paused by a person, Not all measured or Waiting. Enabled is plain text. Paused is a yellow lozenge; the other states are gray. An (i) beside Paused, Not all measured or Waiting says why. In the Severity column, “Low” is gray, “Medium” yellow and “High” red.

• Paused: a reason stops the rule, such as an owner who has not accepted. On Standard, such a rule’s (i) reads “Rules evaluate on the Advanced edition. Existing alerts stay readable.” instead.
• Paused by a person: somebody chose Pause rule.
• Not all measured: the rule runs, but some agreements can’t be measured now.
• Waiting: the license is unconfirmed. The rule resumes by itself.

The row menu holds Edit rule, Pause rule or Resume rule, and Delete rule. The named owner also finds Accept ownership while the rule waits for them, and Withdraw my consent once they accepted a rule somebody else wrote; a Board owner finds Revoke the owner’s consent once someone accepted. Most items need the Board owner role, or they are held with “Changing this rule needs the Board owner role on its board.”

Pause rule stops the rule from evaluating. Its alerts stay readable, and nothing is deleted. The rule then reads Paused by a person, and its menu offers Resume rule, which starts it again. A rule paused for a reason (an owner who has not accepted, a missing field) stays paused until that reason is cleared, as the list at the end of this page shows.

Ownership and consent #

A rule runs as its owner, over the work that person can read. When you name somebody else, the rule waits until they choose Accept ownership in its row menu.

The dialog “Accept ownership of Aging past the SLE?” lists the board’s Classes of service and their queries and the Agreements this rule counts, as they stand now. The rule is then evaluated with their access to Jira. A change by somebody else waits for the owner again.

• Classes of service and their queries: each class with its query, or “This board maps no class of service by a query.”
• Agreements this rule counts: each agreement with its band: “At most 5”, “At least 2”, “Between 2 and 5” or “No limit set”.
• A changed rule: when you accepted before, “Your last acceptance does not cover this rule as it now stands.” stands at the top.
• A class that stops acceptance: a class whose query names a saved filter, or whose query Jira cannot read, holds Accept ownership with “A class of service above must change before you can accept.” A Board owner puts the filter’s own query in the class, or corrects the query.
• While the dialog reads: Accept ownership waits with “Reading what accepting covers.”

The named owner can choose Withdraw my consent, and a Board owner can choose Revoke the owner’s consent. Either one pauses the rule. It then evaluates nothing until somebody names an owner who accepts, or a Board owner takes the rule as You.

Delete a rule #

1. Choose Delete rule in the row’s menu, or on the rule’s page.
2. Read “Delete Aging past the SLE?”. The rule stops evaluating, and every alert row it raised goes with it: open, acknowledged and resolved alike, with their evidence. The number the dialog names counts only the open alerts you can read. Nothing changes in Jira.
3. Select Delete rule.

This cannot be undone. The alerts are described in Risk alerts.

If something looks off #

• “SLE not set; comparison not performed. The rule resumes by itself once the board agrees one.”: a Board owner selects Set it on the rule’s page (Calendar, service levels and classes of service).
• “The named owner has not accepted this rule yet, so nothing is evaluated on their behalf.”: ask the owner to select Accept ownership.
• “This rule reached the most open alerts one rule may hold, counted over every open alert. Acknowledge some and it resumes.”: acknowledge some.
• “Its owner’s acceptance does not cover this rule as it now stands, so nothing is evaluated on their behalf until they accept it again.”: ask the owner to choose Accept ownership again.
• “The owner withdrew their consent. Name an owner who accepts, or take the rule yourself.”: edit the rule and choose another Owner, or You.
• “The named owner no longer holds a role on this board.”: give the owner a role on the board by name again in Access. The rule does not resume by itself: a Board owner then selects Pause rule and Resume rule in its row menu, or edits the rule and names another owner.
• “Every agreement this rule names is switched off, so nothing is compared. …”: a Board owner switches one of the agreements on again.
• “One or more agreements this rule counts are switched off or cannot be measured on their board right now. …”: a Board owner switches those agreements on again; the rule shows Not all measured until then.
• “This board’s settings changed and its figures are not recalculated with them yet, so nothing was compared. …”: wait for the board’s recalculation; the rule is evaluated again after it.
• “The app could not read the Jira group of one or more team agreements this rule counts, …”: ask a Jira administrator to check that the team’s group still exists.
• “Jira did not give the app everything it reads to measure one or more agreements this rule counts, …”: wait; those agreements are measured again once Jira answers in full.
• “This board’s planned dates and links were not read whole, so nothing was compared. …”: a Board owner narrows the board’s source if it holds more unfinished work items than the message names.
• “No unfinished work item on this board has a planned date, so no date was compared. …”: give a work item a planned date in Plan (Timeline, milestones and dependencies), and the rule resumes.
• “The last run could not evaluate this board whole. It resumes by itself.”, “The evidence of one alert names more work items than can be checked whole for each reader, …”, “This board has too few completed first cycles in the last 90 days …”, “A handoff into this board cannot be observed on this value stream right now. …” or “Too few handoffs into this board were completed in the last 180 days …”: nothing is needed; each ends with “It resumes by itself”, and the rule does.
• “An agreement this rule names no longer exists on the board.”: edit the rule and choose the agreements it counts again.
• “The value stream this rule names no longer has a stage before this board.”: edit the rule and choose another value stream.
• “A date field this board plans with cannot be found in Jira, so no date was compared. …”: a Board owner names another date field in the board’s plan settings.
• “This board and the stage before it hold more work in progress, waiting work and recent handoffs than one evaluation can check, so nothing was compared. …”: a Board owner of either board narrows that board’s source.