srcplugins

Agent Prompts for Jira

Reusable instructions for your coding agents, managed directly in Jira. Keep your team’s standards, conventions and workflows consistent across work items.

How it works

Stop repeating the same instructions across Jira work items. Create reusable prompts for coding standards, review guidelines and team conventions, all managed directly in Jira. Add the right prompts to each work item to give your coding agents the context they need. When your standards change, update the original prompt and sync when you’re ready.

  1. Write a prompt. Create a work item of the space’s prompt type. The summary is the prompt’s name; the description holds its instructions, written in Jira’s editor.
  2. Add prompts to a work item. Edit the Agent Prompts field and select up to five prompts from the same space. Add them once the work item exists: the field isn’t on Jira’s Create form.
  3. Save. The instructions are copied into one collapsible Agent Prompts section of the work item’s description, where coding agents that read the work item can access it.
  4. Sync. If you make changes to a prompt, select Sync to apply them to the work item.

Edits to existing prompts won’t appear in work items until you sync. To remove a prompt’s instructions, remove the prompt and Save. Prompts hold up to 4,000 characters. Standard Jira text formatting is supported, including headings, lists, code and links. Embedded content and advanced formatting are not supported.

Finding prompts

The field initially shows the 10 most recent available prompts. Search by name or exact work item key; when a search has more results, select Load more to see them.

Results respect your Jira permissions and may take a few seconds to reflect new or updated prompts.

Retiring prompts

To retire a prompt without deleting it, move it to a status in Jira’s Done category, such as Prompt retired. To make it available again, move it to a status outside Done.

The field and Rovo stop offering retired prompts. Work items that already use one keep it, marked (retired), and you can still sync or remove it there. Rovo can still read a retired prompt by its exact work item key.

Note: Any Done-category status retires a prompt, so don’t use Done to mean approved. Status changes may take a few seconds to appear in search results.

Ask Rovo about prompts

Agent Prompts includes Agent Prompts Assistant, a read-only agent for Rovo, Jira’s AI assistant. To use it, open Rovo Chat and select Agent Prompts Assistant from the agents list.

The agent can search for prompts by name within a space and retrieve their instructions. Searches return up to 20 results. Instructions containing links, strikethroughs or other rich formatting that cannot be safely converted to plain text, or too much formatting to fit one answer, must be viewed directly in Jira.

For example:

  • “Find review prompts in TEAM.”
  • “Which prompts in TEAM are about error handling?”
  • On a work item: “Which prompts in TEAM should I add to this work item?”

The agent appears only where Rovo is available on your Jira site. It reads as you and never changes Jira or runs a coding agent.

Screenshots

Installation

Install Agent Prompts for Jira from its Atlassian Marketplace listing.

You will need:

  • Jira Cloud. Jira Data Center is not supported.
  • A company-managed or team-managed software space (team-managed spaces require manual configuration: a space admin adds the field and the prompt work type, as described under Configuration).
  • An organization or site admin to install the app, and a Jira administrator to set up each space.
  • Rovo on your site, only if you want the Rovo agent. Everything else works without it.

Installing the app changes nothing in your spaces: it creates no work types and changes no screens until an administrator sets up a space, as described below.

Configuration

Each space is set up once. Setup uses two kinds of settings:

  • Agent Prompts settings, which a Jira administrator chooses on the app’s Configure page: open Space settings → Apps → Agent Prompts for Jira, or, for every space, Atlassian Administration’s Connected apps → Installed apps and Configure in the app’s row actions. From Jira, the sidebar’s Apps actions lead there through Manage apps → Take me there.
  • Jira settings, such as fields, screens, work types and workflows, which are changed in Jira itself.

Company-managed spaces

Configure everything from the Configure page. The app makes the Jira changes after you review and approve them.

  1. Select spaces and choose Configure selected. Select an existing work type for prompts or create a new one. Every work item of this type is a prompt, so use a type only for prompts, such as Prompt: Jira’s built-in work types, such as Story, Task or Bug, aren’t offered.
  2. Set page refresh behavior. Under Reload work item after saving prompts, keep each space’s existing setting or turn it on or off. It’s off by default, because reloading can discard other unsaved Jira changes.
  3. Choose work types that should use prompts. The app adds the Agent Prompts field to their edit and view screens.
  4. Review and apply the proposed Jira changes.

The app adds the prompt work type to the space’s work type scheme, adds the Agent Prompts field to the chosen screens, and makes sure the prompt type’s create screen has Summary and Description. Jira also updates field configurations as needed. Workflow transition screens aren’t included in the review.

Limits and considerations

  • One review covers up to 50 screens per space. When one request cannot make all of a space’s screen changes, applying continues with the rest in further steps of the same run. A screen shared by more than 1,000 spaces must be changed in Jira settings instead.
  • Prompts are specific to each space, and new spaces need their own setup.
  • Shared schemes and screens may affect other spaces. The review lists these changes before you approve them.

Team-managed spaces

Team-managed spaces require manual configuration. Jira doesn’t let apps change a team-managed space’s settings, so a space admin prepares the space in Space settings. Then a Jira administrator finishes setup in Agent Prompts.

1. In Jira: Space settings (space admin)

  1. In Fields, choose Add field, select Agent Prompts and add it.
  2. In Work types, choose Add work type and create the prompt work type, for example Prompt. Keep the summary and description on its layout. Use a new type only for prompts: Jira’s built-in work types, such as Story or Task, can’t be chosen.
  3. For each work type that uses prompts, open it in Work types, drag Agent Prompts from Other fields into its layout and choose Save changes.

2. In Agent Prompts: Configure (Jira administrator)

On the Configure page, a Jira administrator selects the space, chooses the prompt work type created above, reviews the change and saves it. This changes nothing in Jira: the app only stores which work type holds prompts. The space’s details then show which work types have the Agent Prompts field on their layout.

Optional: keep prompts off boards

Prompts are regular Jira work items, so they appear on boards and use their work type’s workflow by default. Agent Prompts never changes workflows or boards, so an administrator sets this up in Jira by hand. The result is the same in both kinds of space:

  • The prompt work type has its own workflow with two statuses, Prompt available (To Do category) and Prompt retired (Done category), and a transition each way. Any Done-category status retires a prompt, so don’t add another.
  • Both statuses are hidden on every board.

Company-managed spaces (Jira administrator)

  1. Create the two-status workflow and use it for the prompt work type in the space’s workflow scheme.
  2. Leave both statuses unmapped on each board.
  3. Optionally, give the prompt work type its own screen with only Summary and Description, so the app doesn’t add them to a shared create screen.

Team-managed spaces (space admin)

  1. On the prompt work type, choose Edit workflow, select To Do, choose Replace and enter Prompt available. Replace Done the same way with Prompt retired, which stays in the Done category. Remove In Progress and In Review, choose Update workflow and save it for the prompt work type only.
  2. On the board, choose More (···) → Configure columns and drag both statuses to Hidden statuses (Jira may already have put one there). Remove any emptied column and choose Publish.

The app doesn’t check these settings.

Change or remove a space

A space’s details show its status and let you change the reload preference or reconfigure it. Remove setup from selected spaces clears the app’s settings for those spaces without deleting work items, copied instructions, work types, work type scheme changes or field configuration. It removes the Agent Prompts field only from screens the app added it to, and keeps it where another configured space still uses the screen. For team-managed spaces, choose Remove setup… in their configuration instead: it clears the app’s settings and changes nothing in Jira.

Permissions & data

Requested scopes

  • read:jira-work — find visible prompts and read the source and destination work items.
  • write:jira-work — save the destination description and Agent Prompts field as the current user.
  • manage:jira-configuration — inspect work type schemes and create or attach a prompt type after administrator review.
  • manage:jira-project — read screens and screen schemes, add or remove the Agent Prompts field, and add summary and description to screens after administrator review.
  • storage:app — store space settings, selected prompt IDs and content fingerprints, the latest space configuration, records of screens where the app added the field, and save-recovery records.

Reads and writes run as the current user, so Jira’s normal visibility rules decide what each person can see. Saving requires Edit work items, creating prompts requires Create work items, and configuration requires Administer Jira. A space’s health checks also need Create work items in that space: to check the prompt type’s create fields, and in a team-managed space to show which layouts have the field. Everyday prompt use does not need administrator permissions; resolving an unconfirmed save as an administrator requires both Administer Jira and Edit work items.

Jira stores prompts, copied instructions and each work item’s Agent Prompts field, which lists the prompts selected on it. Forge stores space settings, prompt IDs, content fingerprints, save-recovery records, which screens the app added the field to, and a record of the latest space configuration. It stores no account IDs and does not keep a separate copy of prompt text. The app sends nothing outside Atlassian (it declares no external network access) and does not log prompt content.

Work items, history and copied instructions remain after uninstall. Forge retains app data for 28 days; reinstalling does not restore it automatically.

Requests to the Rovo agent and the content they return are processed by Rovo under Atlassian’s Rovo data policies, which may include third-party models. Rovo processing and retention are separate from the app’s Forge storage.

Troubleshooting

  • A save is rejected for formatting: prompts can use headings, lists, quotes, code, rules, links (http, https or mailto) and text styles such as bold, italic, underline and color. Tables, panels, task lists, mentions, emoji, dates, status lozenges, smart link cards, images and other media are not copied. Replace them with plain text or an ordinary link in the prompt, then save again.
  • A prompt is missing: check its space, work type, status and visibility, and allow for Jira search indexing. Search by exact key. A prompt in a Done-category status is retired and isn’t offered, even by exact key.
  • A space isn’t listed on the Configure page: the page lists up to 200 software spaces. Open Space settings → Apps → Agent Prompts for Jira in that space instead.
  • Instructions look out of date: use Sync. Unless the space reloads work items after saving, reopen or reload the work item to see the updated description.
  • A save fails: the app checks the saved state once, keeps your selection and does not repeat the write. Correct the reported problem and retry, or choose Discard changes. If the outcome is still uncertain, use Check saved state or ask a Jira administrator to review it. After two minutes an administrator can release it, keeping the last saved prompts; then use Sync.
  • The field is not shown: reconfigure the space and choose the work type under Add Agent Prompts to screens; in a team-managed space, add it to the work type’s layout in Space settings.
  • The field shows an error: the message names the cause, such as a space that is not set up. Fix it and choose Try again.
  • The app says there’s no active subscription: Agent Prompts for Jira is a paid app, billed through Atlassian, and works fully during a free trial. Without a subscription, the field and the Rovo assistant can’t search, save or sync prompts, and spaces can’t be configured. Administrators can still run health checks, remove setup, and check and release interrupted saves and configuration changes. Your prompts and settings stay as they are, and everything works again once the site subscribes in Atlassian Administration.
  • The field says the space’s prompt type is one of Jira’s built-in work types: the space was set up with a type such as Story or Task, so Agent Prompts is stopped there and its health shows Needs attention. A Jira administrator uses Reconfigure space to choose or create a work type only for prompts.
  • The Agent Prompts section was edited, moved, copied or deleted: choose Sync. It replaces every Agent Prompts section in the description with one fresh copy of the prompts the field links, whatever was changed in them, and leaves the rest of the description as it is. With no prompts linked, Sync removes them.
  • A linked prompt was deleted: the next Save or Sync removes it from the field and the section and says which prompt it removed. A linked prompt copied with a security level you can’t see stops the save with a message saying so, and nothing changes; a Jira administrator manages who can see it.
  • Space setup was interrupted: completed changes stay in place. Use Check affected space or Check saved progress before continuing, and reuse any work type that was already created.
  • A screen change was uncertain: check the reviewed screens in Jira, then review the space again. The app shows what is left to change and never repeats a write on its own.
  • A space is blocked by a screen: the review names the screen. Choose other work types for that space, change the screen in Jira settings, or review again if the spaces using it could not be read in time.

Finish other description edits before saving. The app detects stale state, but a simultaneous Jira edit can still race its final write.

FAQ

Why can’t I add prompts to a prompt?

Every work item of the space’s prompt work type is itself a prompt, and a prompt can’t use other prompts. On a prompt, the field only explains this; open a work item of another type, such as a Bug, to add prompts. A work item that became a prompt after a setup change can still remove the prompts it already has.

The picker says there are no prompts.

The space has no work items of its prompt work type yet, or none that you can see; the message names that type. Create a work item of that type, give it a summary and a description with the instructions, and it is offered as a prompt. A prompt in a Done-category status is retired and isn’t offered.

Can I use Story or Task as the prompt type?

No. Every work item of the prompt type becomes a prompt, so a type your team also uses for ordinary work would turn that work into prompts. Jira’s built-in work types, such as Epic, Story, Task, Bug and Subtask, aren’t offered or accepted. Choose or create a work type only for prompts, such as Prompt.

Support

For questions, bug reports, or feature requests, email support@srcplugins.com or open an issue on GitHub.