Jira

Assign a Jira issue to Factory or mention @Factory in an issue comment to have Droid investigate, implement, and test the work. Droid runs on a remote computer and reports progress and results in Jira.

You delegate directly from an issue; you do not need to create a Software Factory automation. The Remote delegations settings control the shared execution configuration.

A personal Jira connector gives Droid tools to use inside a session. It does not install the Factory agent in Jira or enable issue assignment.

Prerequisites#

To install and configure Jira delegation, you need:

• A Jira Cloud site with agent assignment and mentions available.
• Permission to install apps and open app administration in Jira.
• The Manager or Owner role in the Factory organization you want to connect.
• Access to Settings → Remote Delegations, including Jira app setup.
• Service-account access and an active service account for shared execution.
• An execution template for Dynamic compute, or service-account-owned Droid Computers for Persistent compute.

Team members who delegate work need a Factory account in the connected organization and permission to use Factory on the Jira issue. Use the same email for Jira and Factory so Factory can link the person making the request.

Install and connect Factory for Jira#

Installing the app and linking the Jira site are separate steps. Complete both before delegating work.

1. 1
   Open Jira delegation settings

   In Factory, open Settings → Remote Delegations. Under Delegation Apps, find Jira and select Set Up for Org.

   If Jira is already connected, select Configure to open its setup page.

2. 2
   Install the Jira app

   On the Jira setup page, select Connect to open Factory for Jira in the Atlassian Marketplace. Select your Jira Cloud site and approve the requested permissions.

   For an existing connection, Manage → Install Jira App opens the same installation page. Installing a personal Jira connector is not a substitute for this app.

3. 3
   Link the Jira site to Factory

   In Jira, open the installed Factory app's Get started or Configure page. Select Connect Factory.

   Factory opens in a new tab. Sign in with a Manager or Owner account and select the intended Factory organization. Review the Jira site and Factory organization shown in the Connect Jira confirmation, then select Connect.

4. 4
   Verify the connection

   Return to the Factory app page in Jira. It should show Connected to Factory. Select Refresh if it has not updated.

   You can also review the Jira app status from Settings → Remote Delegations → Jira → Configure → Manage in Factory. A connected app still needs the execution configuration below before Droid can run work.

Configure shared execution#

In Settings → Remote Delegations, find Remote Delegation Configs and select Edit on Apps.

Follow Configure delegated sessions to review:

• General: default model, reasoning level, and instructions.
• Plugins: the plugins delegated sessions need.
• Identity: an active service account with the required Git credentials and connectors.
• Compute: Dynamic with an execution template, or Persistent with computers owned by the service account.

Eligible organizations receive a default configuration, service account, and execution template. Review those defaults rather than assuming the environment has the repositories, credentials, and tools your task needs.

Jira issue delegations use the Apps configuration's service-account identity and connectors, not the personal credentials of the person assigning the issue. This configuration is shared with other delegation apps, so changes can affect more than Jira.

Team members can set a preferred model and reasoning level under Settings → Session Defaults → Delegations. When organization policy allows it, the requester's model preference overrides the configuration's model. Choose Org default to use the configuration's model and reasoning settings. A personal model preference does not change the service-account identity or connector access.

Delegate an issue#

Before assigning the work, put the repository, desired outcome, acceptance criteria, and verification steps in the issue description. Include relevant error messages, reproduction steps, and links.

For example:

In the storefront repository, investigate the failing checkout test. Fix the cause, run the relevant tests, and open a pull request with the results and a summary of the change.

Assign Factory through the agent picker#

1. 1
   Open the Jira issue.
2. 2
   Select Agents.
3. 3
   Search for Factory and select it to delegate the issue.

Factory appears as a Rovo agent in Jira's Agents picker. You do not need to create a Jira user named Factory.

Mention Factory in a comment#

Add an issue comment, select @Factory from Jira's mention picker, and describe the task. Save the comment to send it.

For example:

@Factory Investigate the failure described in this issue. Fix it in the storefront repository, run the relevant tests, and open a pull request.

Factory uses the issue context and your request to start the session. It can also retrieve issue details, comments, and linked issues through the Jira app's access.

Follow progress and send follow-ups#

Review Factory's progress and replies in Jira's agent conversation. It reports when it is preparing the session, working, or waiting for your reply. For code changes, Droid is instructed to open a pull request and return its URL.

If Droid asks a question, reply in the same agent conversation. You can also send another instruction to refine the work. Only the person who started the delegation can send follow-up messages to that session.

Review the proposed changes and test results before merging. Delegating an issue does not replace code review.

Cancel a running task#

Use the running task's cancellation control in Jira's agent conversation. Factory marks the task canceled and attempts to stop the linked Droid session.

Cancellation does not undo work already performed. Review any changes or pull requests produced before the cancellation.

Troubleshooting#