Requisite documentation
Set up (about 15 minutes)
- Request type. In your service project, create a request type such as "Order from the catalog" with a workflow that has an approval step reading the Approvers field (JSM's "Service request with approvals" workflow does). Keep Summary on the form; Description is optional.
- Jira settings > Apps > Request catalog > Setup. Pick that request type under "Show the catalog on these request types", pick the Approvers field, set the currency, and save.
- Catalog. Add items by hand, or paste a CSV on Import and export (see below).
- Approvals. Add tiers: name, "from total" amount and approvers. Tiers stack.
- Departments and budgets (optional). Add departments with a budget per month, quarter or year and an optional budget owner.
The checklist at the bottom of Setup shows what is still missing.
What requesters see
On the portal create form of the chosen request types: the catalog (search and category filter), each item's price, availability and options, a quantity box, and the cart with the total, the approval reasons and any warnings ("on backorder, about 10 days", "over the department budget"). They can't send the request while a line has a problem (out of stock, over the per-request limit, missing option) or, if you chose "Block", while it is over budget.
After sending, the request page shows Your order with each line's status.
What happens when a request is created
Requisite reads the cart JSM saved with the request, prices it again from the catalog, reserves stock for tracked items, counts the total as pending against the department budget, fills the Approvers field (tiers at or below the total, item approvers, the budget owner if you turned that on, over-budget approvers if over budget, never the requester), writes the order summary as a reply to the customer or an internal note, and makes the order searchable in JQL.
Fulfilling (agents)
The Catalog order panel on the request lists each line:
- From stock (N): hand it out from stock; on hand goes down. Refused if there isn't enough.
- Ordered: bought from the vendor; the reservation is released and the amount is committed.
- Delivered: an ordered line arrived.
- Cancel: drop the line; stock and budget are released.
When the request is resolved with a resolution listed on Setup ("Declined", "Won't Do", "Cancelled"...), every open line is cancelled automatically.
CSV columns
| Column | Also accepted | Notes |
|---|---|---|
| sku | code, item code, part number, product code, id | Required. Matches existing items |
| name | item, title, product, item name | Required for new items |
| category | group, type | |
| price | cost, unit price, amount | 1299.00, $1,299 or 1299 |
| unit | uom | each, seat / month |
| description | details | |
| active | enabled | yes / no |
| stock_tracked | track stock, tracked | turned on automatically when on_hand is given |
| on_hand | stock, quantity, qty, in stock, inventory | whole number |
| low_at | low stock, reorder, reorder point | |
| allow_backorder | backorder | yes / no |
| lead_time_days | lead time | |
| max_per_order | limit, max qty | 0 = no limit |
| option_label | option | e.g. Size |
| option_values | options, variants | S|M|L |
| vendor | supplier | agents only |
Empty cells keep the current value of an existing item. "Check first" shows what would change without saving.
JQL
rcTotal > 1000, rcDepartment = "Marketing", rcState = open (open, partial, done,
cancelled), rcItems >= 5.
Limits
Up to 2,000 items, 100 lines per request, one option group per item, one currency per site, budget periods in UTC. No item images, purchase orders or vendor integration. Requests created by email or API carry no cart.