Visual bug reporting

Bug reporting for Jira, with the evidence in reach

Show the failing step in your website, review what you captured and create a Jira issue with context. The private tautau report keeps the screenshots, recorded steps and diagnostics together for your team.

Connect through your team’s Jira account. Capture still requires a deliberate action and browser permission.

From a website bug to a Jira issue

You will need a tautau workspace with permission to configure projects and a Jira account with access to the destination. Connecting and saving setup does not create a test issue.

  1. Connect the right workspace

    Choose your team workspace, create a project and assign the app under Services. From the project’s Ticket destination, open Integrations and connect Jira. Complete Atlassian consent with an account that can create issues in the intended site.

    Read the connection steps
  2. Choose the Jira destination

    Select the saved connection, Jira site, project and a standard issue type such as Bug. Optionally choose an epic in that project. Review required fields and any defaults, then save the project setup. New destinations begin in manual mode.

    Open project setup
  3. Capture and review the problem

    Open the embedded helper or Chrome reporting flow. Describe the actual and expected behaviour, annotate a screenshot or record the failing steps. Review the images, clips and bounded diagnostics before sending the report to your team.

    Follow the capture guide
  4. Review the ticket before creating it

    Open the saved report in Bug reports and choose Create ticket. Check the body and exact destination, then confirm. A workspace writer can choose to copy reviewed images to Jira. The ticket also contains a private link to the tautau report.

    Read the team review steps
  5. Check delivery and access

    Follow the linked Jira issue and check its contents. The report retains delivery status if something fails. Keep the configured connection current, and make sure the people investigating have access to both the Jira issue and the private tautau evidence.

    Troubleshoot setup and delivery

Review the evidence before the handoff

This real product excerpt shows the reporter checking diagnostics and confirming the review before sending. Jira ticket creation happens later in the configured workspace workflow.

Review the evidence before sending12 seconds · silent

Check the captured diagnostics, confirm the review and send.

Actual product footage · demonstration data · edited excerpt

Open full size
Read what happens
  1. The reporter inspects the captured diagnostics.
  2. They confirm that they have reviewed the evidence.
  3. The report is sent to the private team queue.
Explore the feature

What the Jira issue contains

  • The reported problem, expected behaviour and captured context in the ticket body.
  • Reporter identity and a private link back to the tautau report.
  • The destination and supported field defaults configured for the selected project and issue type.
  • Reviewed images, when a workspace writer explicitly chooses to copy them to Jira.

Evidence links and image copies are different

A private report link requires tautau workspace access. Jira’s permissions do not grant that access. Recordings remain available through the report; this workflow does not promise a video attachment in Jira.

Images copied to Jira become separate files under Jira’s access and retention rules. Automatic ticket publishing does not copy images. Review the intended audience before choosing that extra step.

Check the delivery details

Choose when tickets are created

Manual review

Keep new reports in tautau until a team member reviews the evidence and confirms the ticket destination and body. This is the starting mode for new destinations.

Configured automatic publishing

A configured project can queue Jira issues for eligible completed reports. The project can limit automatic publishing to signed-in reports, leaving guest reports for team review. Required Jira fields must be complete. Automatic publishing does not copy image attachments.

Temporary failures preserve the report and show delivery status. A workspace manager can retry a failed delivery; uncertain provider responses are reconciled before another write. After a successful export, retries return the existing ticket.

Prepare the next report

Start with clear reproduction steps, then add the evidence that helps the next person investigate.