SETUP AND SUPPORT
Get your first report out.
Start here if you already have test2task installed in Chrome. You need an HTTPS Jira Server/Data Center instance and an account allowed to create issues and upload attachments. Jira Cloud is not supported yet.
1. Connect your Jira
Enter credentials in the extension's Settings page, not on this website or in a public support issue.
-
Open Settings from the popup. Enter the final HTTPS Jira base URL.
Include a context path when needed, for example
https://jira.example.test/jira. HTTP and API redirects are not accepted. - Choose authentication. Use a Jira personal access token when your instance supports it. Basic authentication with username/password is a fallback for instances that require it. Use an account with only the access you need.
- Set the project and issue type. Use a real project key and an issue type available in that project, such as Task or Defect. Optional labels, components, priority, and assignee defaults can be left empty for your first test.
-
Test the connection, then save. Test connection calls your Jira's
/rest/api/2/myselfendpoint. Allow Chrome access to the configured Jira origin when requested, then save the settings.
This documentation page does not connect to Jira or receive your credentials. Access to an internal Jira may require your organization's network or VPN.
2. Create a small test report
- Open the webpage you are testing and click the test2task extension icon.
- Enter a short summary and a description of the steps, expected result, and actual result. Start without optional attachments to check issue creation.
- Confirm the project and issue type. Expand More fields and use Load fields if Jira requires additional values.
- Click Create issue. Open the returned issue link and verify the report.
- For a second report, capture a screenshot. Rename it beside the preview or open Annotate to add pen marks, arrows, or text, then Save annotation. Remove any screenshot you do not intend to share.
Capture of a visible tab is not full-page or desktop-wide capture. If an issue is created but an attachment fails, keep its issue link and inspect it before trying another issue submission.
3. Add logs or video when needed
Network and console
Click Record under Network & console. On first use, read the disclosure and choose Start recording. Reproduce the problem, reopen the popup if necessary, and click Stop. Review or download the diagnostic JSON, then explicitly check Attach logs to issue if you want to upload it.
Screen video
Click Record under Screen video and approve the first-use disclosure. The active tab is recorded without audio. Stop the recording, preview or download it, then choose Attach video or export a GIF and select it explicitly.
Remembered approvals
Remember my choice skips the extra disclosure for that recording type on this browser. It does not start recording automatically or select the result for upload. To show the disclosure again, use Settings → Screen recording → Reset recording approvals. Resetting approvals does not stop an active recording or revoke Chrome permissions.
Site storage
Keep this off unless it is useful for the report. Click Review site storage, approve the read and scripting permission if requested, select specific keys, and inspect the JSON before using it. No keys are preselected. This reviewed snapshot is not replaced by a fresh capture during issue submission.
Credential redaction is heuristic, not complete. It does not redact screenshots or video. Review all evidence and avoid uploading secrets or personal information.
Troubleshooting
Connection test returns 401, 403, or 404
401: check the selected authentication method and token/credentials. 403: check account and project permissions. 404: check the base URL and context path. Use the final HTTPS endpoint rather than a URL that redirects to a login or another path.
Jira asks for more fields or rejects an issue type
Use an issue type that exists in the selected project. In More fields, load Jira-required fields and complete the missing values. For an initial test, remove optional defaults that do not exist in that project. Custom JSON must match Jira API field formats.
Record does not start, or a permission error appears
Reload/re-enable test2task at chrome://extensions after updating it and
accept Chrome's permission warning when requested. Click Record and then Start
recording unless approval was remembered. Try a normal webpage rather than a
restricted browser page. For logs, close DevTools on the target tab and stop other
debugger sessions before retrying.
A recording is black or will not play in Jira
First preview or download the complete file from test2task to distinguish a capture problem from Jira player compatibility. Browser support for WebM/MP4 varies; Settings offers MP4 where supported and may fall back to WebM. Browser-restricted or protected content may not be capturable. Include a synthetic reproduction when reporting a problem.
The issue exists, but an attachment is missing
Check the issue link and attachment warning rather than creating another issue immediately. The extension limits each file to 10 MB, and Jira can have a lower limit. Download logs/video when available and attach them manually through Jira if needed. Large videos are not split into byte fragments.
How do I clear captured data or credentials?
Clear individual captures or reset the draft when finished. Clear Credentials in Settings removes stored Jira credentials but does not revoke the token in Jira. Revoke tokens through your Jira account separately. Local deletion does not delete downloaded files or content already uploaded to Jira.
Still need help?
Use the public GitHub tracker for bugs, questions, and feature requests. A GitHub account is required to submit an issue.
Open a support requestInclude the extension and Chrome versions, operating system, affected feature, reproduction steps, and sanitized error message. For a privacy question, read the privacy policy and request a private contact channel before sharing sensitive details.