Jira Integration

Integrating Robonito with Atlassian Jira creates a seamless bridge between your automated testing pipeline and your active development backlog. When a test officially fails in Robonito, QA engineers can immediately generate a complex bug ticket directly from the dashboard without switching context.

1. Connecting Your Jira Workspace

To connect Jira, you must grant Robonito secure OAuth access to interact with your Atlassian projects:

  1. Navigate to Integrations: In the main Robonito dashboard, open the Integrations tab from the left sidebar.
  2. Select Jira: Locate the designated Jira tile and click Connect.
  3. Authorize Access: A secure browser window will open requesting Atlassian OAuth permissions explicitly. Follow the on-screen prompts to grant access safely.
  4. Confirm: Return to Robonito; the status panel will display Connected.

2. Configuring Ticket Defaults

To dramatically speed up the bug-logging workflow, configure your default project mapping variables:

  • Site: Set the default Atlassian URL (if your organization uses multiple Jira instances).
  • Project: Select the primary Jira Board/Project where engineering bugs are tracked.
  • Assignee: Assign a default team member (e.g., your QA Lead) who will triage the incoming bug.
  • Issue Type: Default to standard classifications like Bug or Task.

These defaults are flexible and can be manually overridden when creating individual tickets.

3. Creating a Jira Bug Ticket

When an automation suite eventually fails, you can leverage the integration directly from the failure forensics screen:

  1. Review Failure Logs: Open the Execution Report for the failing test case.
  2. Log a Bug: Click the Log a Bug action button prominently displayed near the failed step. Log a Bug Button UI
  3. Edit the Ticket Details:
    • A creation module will open, pre-filled with your default Jira Project and Assignee.
    • Summary: Write an actionable bug title.
    • Description: Robonito autonomously injects deep failure logs, DOM state output, and direct image snapshot URLs into the body of the ticket. Add any manual QA context required.
  4. Submit: Click Create Ticket to push the comprehensive report directly into your developer's Jira backlog pipeline.