[changelog] [Added] UI modifications support for Jira Service Management agent view now in Preview

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
api, devtools

Research direction

Start by locating the simulated jira:uiModifications module surface and the bridge implementation for view.getContext(). Then inspect any mocked UI modifications REST API routes. Done means the three agent viewType values are accepted, requestTypeId is exposed in agent-view context, and the mocked routes tolerate those values without rejecting existing behavior.

Written by the indexing model from the issue text.

Description

upstream-changelog

GUID: CHANGE-3394
pubDate: Mon, 17 Aug 2026 03:18:33 GMT
Category: Added

What's changing

UI modifications (the existing jira:uiModifications module) now support Jira Service Management agent views, in Preview. Three new view types are added:

  • Global issue create (GIC): viewType: GICAgentView
  • Issue view: viewType: IssueViewAgentView
  • Issue transition: viewType: IssueTransitionAgentView

Details:

  • Agent views support the same fields/methods as the equivalent Jira views, tailored for service projects.
  • Extension context exposes the requestTypeId of the work item.
  • The supported field set differs from the JSM request create portal view.
  • The UI modifications REST API (GET/POST/PUT) now accepts these three agent view types. When configuring agent view contexts: portalId must not be set, requestTypeId is optional (omitting it = not scoped to a request type). One of projectId, issueTypeId, or viewType can act as a wildcard, with a maximum of one wildcard per context.
  • view.getContext() can be used to detect the current view type.

Parity impact for forge-sim

Area: modules + context hydration (bridge view.getContext()). If/where forge-sim simulates the jira:uiModifications module surface, the simulated extension context should accept the three new viewType values and expose requestTypeId in the agent-view context. Any mocked UIM REST API routes should tolerate the new view types. Additive change; no existing behavior is altered, but rendering/invoking a UIM module with one of these viewTypes should not be rejected by the simulator.

Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3394

Dominant language
TypeScript
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.