Intake Standards for Jira Service Management Documentation All pages

The settings page

Each project has its own Intake standards page, under Project settings. This is where a project admin writes, tries, enables and reviews the standard for each work type.

Opening the page

Project settings, Intake standards. The page is open to people with Administer Projects on that project. Every request the page makes is checked on the server, so the page's address is no use without that permission.

A standing message above the page tells you when checks are paused on the site: "Subscription inactive" when the subscription has lapsed, or "Run budget used up" when the month's runs are spent. From 80 % of the budget it reads "Run budget nearly used up".

The work types

A sidebar lists the project's work types, each with its state: "v3 enabled" for a work type whose version 3 is live, "Not enabled" when its versions have all been retired, "Draft" beside either when a draft is open, and "None" when it has never had a version. Select a work type to act on it in the four tabs.

Checks

The Checks tab shows the enabled version read-only and the draft you can edit. A work type has at most one draft. A new standard starts from a template or from an empty draft. A standard holds:

Save draft keeps your changes. A draft can be saved and evaluated as often as you like; nothing reaches requesters until you enable it.

Versions

The Versions tab lists every version of the work type's standard: the draft, the enabled version and the retired ones, with who saved and enabled each and when. Enabled and retired versions cannot be changed.

Evaluate

The Evaluate tab shows the requester's box and checklist for any version, drafts included. Paste a text and run it, and you see the verdicts, quotes and hints a requester would see, with how long the run took. Evaluations write nothing to the run log or to any work item.

Each installation can run 200 evaluations a day. The count starts again at 00:00 UTC, and every run counts, including one that fails or is under the word minimum. Evaluations draw on the same Forge LLMs allowance as requesters' checks, and count towards the site's monthly run budget. The tab is paused while the subscription is inactive, and refused once the month's budget is used up.

Run log

The Run log tab lists every check against an enabled version, from the customer portal or the agent view, for 30 days: when it ran, the source, the outcome, the version, the request key once the request exists, and how long it took. Open a run to see the requester's text and each check's verdict with its quote or hint. A line above the filters shows the month's usage, for example "1,240 runs this month of 3,000". Your data sets out what a run log row holds and who can see it.

Changing a standard

An enabled version cannot be changed. Edit the draft on the Checks tab, or Copy to draft from an earlier version on the Versions tab, then save, evaluate and enable. Enabling the new version retires the old one. A form that is already open keeps the version it loaded until it is reloaded. Every save and enable records who did it and when, and Compare lists what changed between two versions.

Disabling a standard

To stop checking a single work type without a deploy, open the Versions tab for that work type and disable the enabled version. Disabling asks for confirmation and retires the version. From then on the work type has no enabled standard: every form opened afterwards shows a plain required box, and nothing is checked or flagged. A requester who already has the form open must reload it. Other work types carry on as before. To start checking again, enable a version from the Versions tab.