Project113

Item Policies

Item policies automate how items behave when they are created. They can set defaults, enforce permissions, auto-assign assignees, and mark stale items. Policies are managed from the item section of the repository's Settings page.

Policy Targets

A policy applies to specific subjects you choose: individual members, roles, groups, or audiences. This lets you create different rules for different teams or permission levels.

Permission Rules

Each policy can allow or deny permissions for items, assignees, threads, and dependencies. This is a powerful way to enforce per-item behavior across matching items.

Item Settings (Defaults)

For matching items, a policy can set defaults applied when the item is created:

  • Default state — Set the state of newly created matching items.
  • Default type — Set the item type of newly created matching items.
  • Pin new items — Automatically pin matching items.
  • Auto stale (days) — Mark matching items as stale after this many days of inactivity.

Pattern Matching

Policies match items using SQL LIKE patterns (% matches any sequence, _ matches exactly one character):

  • Title patterns — Match items whose title contains the pattern (for example, %fix% or *release*).
  • Type patterns — Match items whose type matches the pattern (for example, bug or feature).

Patterns are comma-separated; multiple patterns can be provided. A pattern of % matches everything.

Assignee Rules

Assignee rules (gated by the assignee_policies permission) automatically assign specific members to matching items when they are created. Each rule picks an assignee and can use the same title and type patterns to scope when the assignee is applied.

Priority

When multiple policies apply to an item, the one with the highest priority wins. This allows fallback rules — for example a general policy for all items with a higher-priority override for items that match a specific title pattern.

Stale Detection

Items are automatically marked Stale after a configured number of days without activity. The stale window can be configured per policy, and individually per item. A value of 0 means the item is never marked stale.

Where to Manage Policies

Item policies (and assignee rules) are created, edited, and deleted from the repository Settings page under Item Policies. The actions require the policies and assignee_policies permissions respectively.