Version 1.0 · Complete registry

Widget Reference

Every registered Customer Portal Toolkit widget, what it shows, when to use it, where it can render and what administrators must verify.

The registry contains 62 contracts. The builder exposes 61 portal/customer widgets; Admin AI Configuration Assistant is admin-only.

Updated July 21, 2026 · Availability still depends on the installed version, project capabilities, Jira permissions and the selected portal area.

A coordinated customer request view built from several independent widgets.

Find a widget

Showing all 62 widget definitions.

Registry presence is not tenant capability. A widget can remain unavailable when a required field, API, plan, workflow, account type, license or permission is missing. Safe unavailable states are intentional and do not authorize a substitute data source.
33 definitions

Information and layout

Information and layout widgets turn authorized request data and configured content into a clearer customer view.

Information and layout widgets turn authorized request data and configured content into a clearer customer view.
jira-field

Generic Jira Field

#

Displays one customer-visible Jira field using a supported renderer and a customer-facing label.

Use it when
You need to surface a specific approved field without changing the Jira value.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Select a field exposed in the current project; missing or unsupported field types fail locally.
multi-field-summary

Multi-field Summary

#

Groups several approved request fields into one compact summary.

Use it when
Customers need a concise overview such as status, priority and created date.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Keep the list short and confirm every selected field is customer-visible.
assignee-card

Assignee Card

#

Shows the safe presentation of the current request assignee.

Use it when
Customers benefit from knowing who is handling the request.
Source
Current request
Surfaces
Request details and side panel
Configure or check
The card cannot reveal identifiers or data Jira does not expose to the current user.
team-card

Team Card

#

Presents an approved team or ownership field as a customer-friendly team card.

Use it when
A service team or resolver group is more useful to customers than an individual name.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Map an appropriate current-project field and provide a safe empty-state label.
reporter-card

Reporter Card

#

Shows the customer-safe presentation of the request reporter.

Use it when
The requester identity helps clarify who raised a shared request.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Jira request access still controls whether the value is available.
participants

Participants

#

Lists safe names and avatars for authorized request participants.

Use it when
Customers need to understand who is included in a shared request.
Source
Request participants
Surfaces
Request details and side panel
Configure or check
IDs, email addresses and self links are stripped from the customer projection.
organization

Organization

#

Shows the request organization in a compact customer-safe presentation.

Use it when
Organization membership is relevant to the request context.
Source
Organizations
Surfaces
Request details and side panel
Configure or check
Availability depends on JSM organization data and the current user's access.
status

Status

#

Displays the current Jira/JSM request status with an accessible status treatment.

Use it when
The raw workflow state is already meaningful to customers.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Use Status Explanation as well when internal workflow wording needs customer context.
status-explanation

Customer-friendly Status Explanation

#

Adds reviewed plain-language text explaining what the current status means and what happens next.

Use it when
Workflow labels alone do not set a clear expectation.
Source
Current request plus configured content
Surfaces
Request details and side panel
Configure or check
Write and review localized explanations; do not present an SLA promise unless one exists.
priority

Priority

#

Shows the current request priority in a customer-friendly format.

Use it when
Priority is intentionally visible and useful to the customer.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Confirm the project exposes the priority to the customer; avoid implying response guarantees.
date

Date

#

Formats a selected approved date value for customer display.

Use it when
A project-specific date should be easier to read than the raw Jira value.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Select the intended date field and verify timezone/empty-value behavior.
due-date

Due Date

#

Displays the Jira due date with customer-friendly formatting.

Use it when
The request has a meaningful customer-facing target date.
Source
Current request
Surfaces
Request details and side panel
Configure or check
A due date is not automatically an SLA commitment; explain the business meaning in the label.
sla

SLA

#

Shows a selected customer-visible SLA cycle, including safe running, paused or completed states.

Use it when
JSM exposes an SLA that the customer should understand.
Source
SLA
Surfaces
Request details and side panel
Configure or check
Requires the SLA capability and a compatible field/cycle in the current project.
time-remaining

Time Remaining

#

Presents the remaining time from an available customer-visible SLA cycle.

Use it when
Customers need a compact view of an active SLA countdown.
Source
SLA
Surfaces
Request details and side panel
Configure or check
Handles missing, paused and completed cycles without inventing a duration.
last-public-update

Last Public Update

#

Shows when the most recent public customer-visible comment was added.

Use it when
Customers need to know how recently the service team communicated publicly.
Source
Public comments
Surfaces
Request details and side panel
Configure or check
Private comments are never requested or considered.
last-status-change

Last Status Change

#

Shows the latest safe request status-change timestamp.

Use it when
The age of the current workflow state is useful context.
Source
Issue history
Surfaces
Request details and side panel
Configure or check
The widget remains unavailable when a safe status timestamp cannot be derived.
request-age

Request Age

#

Shows how long the current request has existed.

Use it when
Elapsed request age helps orient the customer.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Treat age as context, not as a response or resolution commitment.
service

Service

#

Displays the authorized service associated with the request.

Use it when
A named service helps customers connect the request to the affected business service.
Source
Services
Surfaces
Request details and side panel
Configure or check
Availability varies by JSM plan, project setup and request field data.
assets-object-card

Assets Object Card

#

Shows a bounded customer-safe projection of a linked Jira Assets object.

Use it when
A device, application or configuration item is relevant to the request.
Source
Assets
Surfaces
Request details and side panel
Configure or check
Requires Assets and an approved linked object/field; arbitrary object data is not returned.
knowledge-article

Linked Knowledge Article

#

Links to an approved knowledge article associated with the request.

Use it when
A customer-facing article can help explain or resolve the issue.
Source
Confluence/JSM knowledge
Surfaces
Request details and side panel
Configure or check
Requires the knowledge-base capability and a link the current context may expose.
working-hours

Working Hours

#

Presents configured or service-desk working hours in a readable schedule.

Use it when
Customers need to understand service availability windows.
Source
Service desk
Surfaces
Request details and side panel
Configure or check
Requires compatible service-desk data; keep timezone and holiday wording explicit.
static-text

Static Text

#

Publishes localized, sanitized administrator-written content.

Use it when
You need guidance, policy text, contact details or context that does not depend on a request value.
Source
Configuration
Surfaces
Request details, side panel and portal header
Configure or check
Portal-header use may be public; never include secrets or request-specific content.
heading

Heading

#

Adds a localized semantic heading that structures a panel.

Use it when
A group of widgets needs a clear customer-facing section title.
Source
Configuration
Surfaces
Request details, side panel and portal header
Configure or check
Keep heading levels and wording meaningful; do not use headings only for visual size.
callout

Callout

#

Highlights a localized information, success, warning or critical message.

Use it when
A customer should notice an important instruction or service notice.
Source
Configuration
Surfaces
Request details, side panel and portal header
Configure or check
Choose a truthful severity and keep public-header messages explicitly public-safe.
button

Button

#

Presents a configured link as a prominent button without performing a Jira mutation.

Use it when
A safe external or portal destination is the primary next step.
Source
Configuration
Surfaces
Request details, side panel and portal header
Configure or check
This is a navigation control, not an action widget; use action widgets for Jira changes.
divider

Divider

#

Adds a quiet visual separator between content groups.

Use it when
A long panel needs visual structure without another heading.
Source
Configuration
Surfaces
Request details, side panel and portal header
Configure or check
Decorative only; it has no independent content or appearance configuration.
spacer

Spacer

#

Adds controlled vertical spacing between layout elements.

Use it when
A small amount of breathing room improves scanning.
Source
Configuration
Surfaces
Request details, side panel and portal header
Configure or check
Use sparingly; excessive spacing harms mobile and keyboard reading flow.
progress-bar

Progress Bar

#

Shows a bounded visual progress value derived from approved request data.

Use it when
A request has a meaningful, explainable completion measure.
Source
Current request
Surfaces
Request details and side panel
Configure or check
Provide a text equivalent and never infer progress from unsupported workflow assumptions.
process-timeline

Process Timeline

#

Presents configured process steps and the current position as an accessible journey.

Use it when
Customers benefit from understanding the expected request lifecycle.
Source
Current request plus configured steps
Surfaces
Request details and side panel
Configure or check
Keep steps aligned with the real workflow and review them after workflow changes.
14 definitions

Metrics and counters

Metrics return generalized presentations with privacy, sample and freshness context—not matching request rows.

Metrics return generalized presentations with privacy, sample and freshness context—not matching request rows.
open-issues-counter

Open Issues Counter

#

Shows a privacy-treated count or generalized presentation of open requests in the current project.

Use it when
Explain current service workload without exposing request rows.
Source
Aggregate query
Surfaces
Request details and side panel
Configure or check
Default query excludes Done; privacy thresholds, freshness and differencing controls apply.
new-issues-counter

New Issues Counter

#

Shows a privacy-treated view of recently created requests.

Use it when
Provide recent demand context, typically over a bounded seven-day window.
Source
Aggregate query
Surfaces
Request details and side panel
Configure or check
Use a legitimate cohort and customer-safe wording; no matching request list is returned.
similar-issues-counter

Similar Issues Counter

#

Shows a privacy-treated count for a configured project-bound similarity/query definition.

Use it when
Tell customers that comparable demand exists without identifying other requests.
Source
Aggregate query
Surfaces
Request details and side panel
Configure or check
The query is not a free-text search over customer content and may be suppressed for small cohorts.
current-load-level

Current Load Level

#

Converts a safe aggregate into a qualitative current workload level.

Use it when
A simple Low/Moderate/High message is more useful than an exact count.
Source
Aggregate query
Surfaces
Request details and side panel
Configure or check
Document thresholds and avoid presenting the level as a response-time promise.
historical-comparison

Historical Comparison

#

Compares a prepared metric with a prior safe baseline.

Use it when
Customers need context such as above, near or below the recent baseline.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Requires stored snapshots and sufficient sample; it can remain unavailable while history is building.
trend-indicator

Trend Indicator

#

Shows the direction of a prepared historical metric with context and freshness.

Use it when
A rising, stable or falling service trend helps explain current conditions.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Trend is descriptive, not predictive; include sample/freshness and a text label.
typical-first-response

Typical First Response Time

#

Shows a privacy-treated historical first-response duration.

Use it when
Set realistic context about past service behavior without promising an individual response.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Requires the semantic metric engine, safe sample and freshness; it is not an SLA guarantee.
typical-resolution

Typical Resolution Time

#

Shows a privacy-treated historical resolution duration.

Use it when
Give customers historical resolution context for comparable requests.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Requires accepted resolution semantics; never relabel a generic issue count as a duration.
percentile-response

Percentile Response Time

#

Shows a configured response-time percentile from safe historical samples.

Use it when
Communicate distribution context beyond an average.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Explain the percentile and sample; the value remains contextual, not a promise.
organization-requests

Organization Requests Summary

#

Shows a privacy-treated project aggregate constrained to an organization the current user belongs to.

Use it when
A customer organization needs generalized context about its requests.
Source
Organization requests
Surfaces
Request details and side panel
Configure or check
Membership is verified as the current user; missing or unverified organization fails closed.
customer-requests

Customer Requests Summary

#

Shows a privacy-treated aggregate constrained to the current customer account.

Use it when
A customer needs generalized context about their own request activity.
Source
Customer requests
Surfaces
Request details and side panel
Configure or check
Requires an authenticated customer account; anonymous or missing account context fails closed.
sla-success-rate

SLA Success Rate

#

Shows a privacy-treated historical percentage for an accepted SLA definition.

Use it when
Provide historical service-level context across a sufficiently large sample.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Requires a valid SLA metric, safe sample and freshness; it is not a guarantee for the current request.
custom-jql-counter

Custom JQL Counter

#

Runs a validated, project-bound administrator query and returns only a privacy-treated scalar presentation.

Use it when
A supported preset cannot express the required legitimate cohort.
Source
Aggregate query
Surfaces
Request details and side panel
Configure or check
Use supported variables and fields only; no arbitrary endpoint or matching issue rows are exposed.
visual-query-counter

Visual Query Counter

#

Builds a project-bound count using a controlled visual rule editor instead of raw JQL.

Use it when
Administrators need a safer guided way to define a cohort.
Source
Aggregate query
Surfaces
Request details and side panel
Configure or check
Rules use allowlisted fields/operators/values and the same privacy, cost and freshness controls.
3 definitions

Charts

Charts use prepared privacy-treated snapshots and always include a text equivalent.

Charts use prepared privacy-treated snapshots and always include a text equivalent.
mini-line-chart

Mini Line Chart

#

Displays a short prepared time series as an accessible line chart.

Use it when
Direction over time is more useful than one scalar value.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Uses stored snapshots only in customer runtime and includes a text equivalent.
mini-bar-chart

Mini Bar Chart

#

Displays a short prepared series or bounded buckets as an accessible bar chart.

Use it when
Customers should compare a small set of safe periods or categories.
Source
Historical metrics
Surfaces
Request details and side panel
Configure or check
Keep bucket labels clear; suppressed/no-data states never invent demonstration values.
donut-chart

Donut Chart

#

Shows a bounded privacy-treated composition with an accessible text summary.

Use it when
A small number of safe categories explains the makeup of a cohort.
Source
Historical/aggregate metrics
Surfaces
Request details and side panel
Configure or check
Avoid too many slices and ensure every category passed privacy controls.
3 definitions

Optional AI

AI is optional, administrator-controlled and backed by deterministic fallback. One AI contract is admin-only.

AI is optional, administrator-controlled and backed by deterministic fallback. One AI contract is admin-only.
ai-summary

Customer-safe AI Summary

#

Optionally summarizes bounded public request data already authorized for the current actor.

Use it when
A concise, labeled overview can help customers understand a long customer-visible request.
Source
Forge LLM
Surfaces
Request details and side panel
Configure or check
Off by default; requires global and widget opt-in, budget, validation and deterministic fallback.
plain-language-explanation

Plain-language Explanation

#

Optionally rewrites bounded authorized context into simpler customer language.

Use it when
Technical status or request context needs a plain-language aid.
Source
Forge LLM
Surfaces
Request details and side panel
Configure or check
Treat output as assistance, not authoritative Jira state or legal, HR, security, financial or safety advice.
admin-ai-assistant

Admin AI Configuration Assistant

#

Defines an optional admin-only assistance contract for supported configuration tasks.

Use it when
An administrator wants help drafting supported customer-facing configuration where the released admin surface provides it.
Source
Forge LLM
Surfaces
Administrator only; no customer portal location
Configure or check
This is the 62nd registry contract, not a portal widget. It never publishes itself or executes Jira actions.
9 definitions

Customer actions

Actions require confirmation and repeat permission, workflow and published-policy checks on the server.

Actions require confirmation and repeat permission, workflow and published-policy checks on the server.
edit-fields

Edit Allowed Fields

#

Lets a customer edit one configured allowlisted request field after fresh server validation.

Use it when
A supported scalar field should be safely editable from the request view.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
The server rejects missing, extra, incompatible or oversized field input; Jira validation remains authoritative.
add-public-comment

Add Public Comment

#

Lets the current customer add a required public comment of up to 10,000 characters.

Use it when
A clear customer-visible update is the intended next action.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
Always public; private/internal comment APIs are not used.
add-attachment

Add Attachment

#

Uploads one supported local file from 1 to 256 KiB as the current customer.

Use it when
A small supporting file is needed on the request.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
Filename, MIME type, base64 and size are bounded; retest customer attachment permission.
add-participant

Add Participant

#

Lets a customer choose an administrator-approved participant label backed by a tenant-bound server token.

Use it when
A known approved participant may be added to the request.
Source
Action capabilities plus tenant-hosted policy
Surfaces
Request details, side panel and request action
Configure or check
The browser never receives or submits a raw account ID; execution resolves and rechecks the published token server-side.
confirm-resolution

Confirm Resolution

#

Offers only a current customer-visible transition that matches the published allowlist.

Use it when
The workflow exposes an approved transition for confirming resolution.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
Available transitions are intersected with the live current-user workflow immediately before execution.
request-reopen

Request Reopen

#

Offers an approved current customer transition for reopening or requesting reopening.

Use it when
The service workflow explicitly permits this customer transition.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
There is no privileged bypass; a missing current transition leaves the action disabled.
escalate-request

Escalate Request

#

Offers an approved customer-visible workflow transition labelled as escalation.

Use it when
The current workflow has a real permitted escalation path.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
The label does not create elevated authority; only the live allowed transition can run.
customer-transition

Customer-accessible Transition

#

Presents a generic select of current customer transitions intersected with configured transition IDs.

Use it when
A project needs a supported transition that does not fit the named action widgets.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
Only server-attested current transitions appear; workflow changes require retesting.
custom-safe-action

Custom Safe Action

#

Runs a closed registered safe operation; version 1.0 supports a configured public-comment body only.

Use it when
A reviewed fixed operation fits the closed safe-action contract.
Source
Action capabilities
Surfaces
Request details, side panel and request action
Configure or check
No arbitrary URL, HTTP method, headers, payload, script or code can be configured.

Rules shared by every widget

  • The backend derives site, environment, actor, project, request, request type, module and license from trusted Forge/Jira context.
  • A portal location is checked again at runtime; registry compatibility alone is not authorization.
  • Missing values, capabilities or source failures stay local to the widget and do not expose privileged data.
  • Customer aggregate widgets never return matching request rows, issue keys, summaries, people, comments, organizations or field values from other requests.
  • Actions require an authenticated current customer, active license, visible published widget, current Jira/JSM permission, compatible workflow, confirmation, idempotency and rate limits.
  • New widgets use the compact borderless JSM-native appearance unless an administrator explicitly selects another validated preset.

For configuration workflow, preview, publication and acceptance, return to the complete user guide. For a missing or disabled widget, use Troubleshooting.