Atlassian Forge · Jira Service Management

Run JSM actions as the
right agent, every time.

Proxy Agent lets administrators and authorized agents post comments, transition issues, and edit fields on behalf of another service desk agent, with a full audit trail.

Focused tools for Atlassian Cloud teams.

Qwerty Craft builds focused, opinionated tools for Atlassian Cloud teams. We're a small independent vendor, and every app we ship is designed to do one job well, runs natively on Forge, and respects your data residency and security posture by default.

Native on Forge

Runs entirely on Atlassian's serverless platform, with no external servers and no data leaving your tenant.

One job, done well

No bloated suites. Each app solves a specific problem with a small, predictable surface area.

Secure by default

Permission checks gate every privileged action, and every change is written to an immutable audit log.

Proxy Agent

An Atlassian Forge app for Jira Service Management (Cloud) that lets approved users perform actions on a JSM request as another configured service desk agent, instead of as themselves or as a generic app actor.

Use cases

  • Out-of-hours coverage. A senior agent takes an action while attributing it to the assigned agent.
  • Automation review. Route automated comments through a designated "service desk bot" user with a real name and avatar customers recognize.
  • Delegated administration. Admins resolve tickets without polluting the customer-visible history with their own identity.
  • Identity hygiene. Avoid "Atlassian Marketplace App" appearing in customer-visible activity feeds.

Key capabilities

  • Act-as-agent issue action. A modal on JSM requests with tabs for Comment, Transition, Edit Issue, Update Links, and Time Tracking.
  • Global and per-project configuration. Pick the default acting identity at the app level, override per project, or fall back to "app" mode.
  • Forge project permission. An app-defined `act-as-agent` permission gates who can invoke the proxy action and respects per-issue scheme rules.
  • Full audit log. Every action is stored with timestamp, issue, project, acting user, target user, mode, success/failure, and error detail.
  • Multi-language UI. English, German, French, Italian, Spanish, Turkish, Japanese, Brazilian Portuguese, Simplified & Traditional Chinese, Korean, Russian, Polish, and Dutch.
  • Built on Forge. Runs entirely on Atlassian’s serverless platform. No external servers, and no customer data leaves Atlassian’s infrastructure.

Three steps from install to audit-logged.

No external services, no extra accounts. Install from Marketplace, configure once, and start attributing actions to the right agent.

01

Install

Install Proxy Agent from the Atlassian Marketplace into your Jira Cloud site.

02

Configure

Set the default acting agent globally and (optionally) per service desk project. Grant the Act as Agent project permission to the roles you trust.

03

Use

Trigger the Act as Agent action on any JSM request. Comments, transitions, and field updates are posted under the configured agent’s identity, and written to the audit log.

Forge-native. Your data stays in your tenant.

Proxy Agent runs entirely on Atlassian's serverless Forge platform. There are no external servers, no third-party processors, and no path for customer data to leave Atlassian's infrastructure.

  • ✓ Sandboxed Forge runtime, hosted by Atlassian
  • ✓ Encrypted Forge storage, in your Atlassian region
  • ✓ Forge-managed authentication, with no tokens or passwords stored by the app
  • ✓ Impersonation gated by an app-defined project permission and an immutable audit log
Read the full security overview

Talk to a real human at Qwerty Craft.

Whether you're a Marketplace reviewer, a Jira admin evaluating Proxy Agent, or a customer who needs help, write to us directly.

General & sales

Questions about the product, pricing, or vendor information.

ata@qwertycraft.com
🔒

Security & legal

Vulnerability reports, privacy requests, or legal questions.

ata@qwertycraft.com