How it works
- Create a prompt ticket. Give it a name in Summary and write the instructions in Description using Jira’s editor.
- Choose prompts for a work ticket. Select up to five prompts from the same project in the Agent Prompts field.
- Save the instructions. Save copies their content into one collapsible Agent Prompts section in the ticket’s Description.
- Update when you’re ready. After editing a source prompt, use Sync on a linked ticket to copy the latest instructions for its saved selection.
Source edits do not automatically update existing tickets. Text, headings, lists, quotes, and code are supported, with up to 4,000 text characters per prompt. Embedded cards, media, and unresolved synced references are not supported.
Installation
Public installation is not available yet. A verified installation link and release instructions will be added here when the plugin is ready.
Configuration
A Jira administrator opens Project configuration, selects the projects to configure, and chooses an existing prompt ticket type or creates a new one. The administrator reviews the proposed changes before applying them. Installing the app alone does not create ticket types.
Add the Agent Prompts field to work-ticket screens. Prompt sources stay within their own project; newly created projects need separate configuration. Screens, workflows, and board layouts are managed in Jira administration.
Permissions & data
The app reads accessible Jira tickets and saves Description and Agent Prompts changes as the current user. Saving requires Edit Issues; creating prompts requires Create Issues. Configuration requires Administer Jira.
read:jira-work— find prompt tickets and read source and destination content.write:jira-work— save copied instructions and the selected prompts.manage:jira-configuration— inspect ticket type schemes and create or attach types after administrator review.storage:app— retain project settings and records used to track and recover saves.
Jira stores prompt content and copied instructions. Forge stores configuration, source IDs, and tracking and recovery metadata; it does not store a separate prompt-content library. The app declares no external network egress and does not log prompt content.
The development version also includes a read-only Rovo assistant for finding and reading prompts. Requests and returned prompt text are processed by Rovo under Atlassian’s policies, separately from the app’s Forge storage. It does not run coding agents or make chat-driven ticket changes. Broader user-permission and Rovo behavior checks are still in progress.
Troubleshooting
- A new prompt is missing: check its project and configured ticket type, allow for Jira search indexing, then reopen the field.
- Instructions look out of date: use Sync for the saved selection, then reopen or reload the ticket to see the updated Description.
- A save fails: the app checks saved state once without repeating the write. Review the reported problem before saving again. If the outcome is uncertain, reopen the field and ask your Jira administrator to inspect it.
- The copied block was edited or removed: the app stops the save when it cannot safely identify its tracked content. Resolve the reported conflict before continuing.
Availability
No public release yet. The current version is being tested in development. Production readiness, broader user access, and coding-agent integrations remain under verification.