User Rating 0.0 ★★★★★

Total Usage 0 times

Category Document Converters

Drop your db-1.0.json file here or click to browse Supports Bitbucket Cloud export format (max 50 MB)

Is this tool helpful?

Your feedback helps us improve.

★ ★ ★ ★ ★

About

Bitbucket's issue tracker export produces a db-1.0.json file containing issues, comments, attachments metadata, and version history. Losing access to a hosted repository means losing that issue history unless it has been converted to a portable format. This tool parses the exported JSON structure, joins each issue with its associated comments by matching issue_id fields, and generates a self-contained HTML document. The output requires no server, no database, and no runtime dependencies. It renders in any browser as a permanent archive. Note: the converter assumes Bitbucket Cloud export schema (version 1.0). Older on-premise exports may use different field names and will fail validation.

Formulas

The converter performs a join operation between the issues collection and the comments collection. For each issue I_k, the set of associated comments C_k is determined by matching the foreign key:

C_k = { c ∈ Comments | c.issue = I_k.id }

Comments within each set are sorted chronologically:

C_k^sorted = sort(C_k, created_on, ASC)

The total output size S in characters is approximately:

S ≈ n∑k=1 (T_k + |C_k|∑j=1 c_j)

where T_k is the template overhead per issue (HTML wrapper, metadata fields) and c_j is the rendered length of each comment. The content sanitization pass applies HTML entity escaping: & → &, < → <, > → > before any markup rendering to prevent XSS in the output file.

Reference Data

JSON Field	Type	Description	Required	Example Value
id	integer	Unique issue identifier	Yes	42
title	string	Issue title / summary	Yes	Fix login redirect
status	string	Current state	Yes	open, resolved, closed, on hold, invalid, duplicate, wontfix
priority	string	Severity level	Yes	trivial, minor, major, critical, blocker
kind	string	Issue classification	Yes	bug, enhancement, proposal, task
content	string	Issue body / description text	No	Markdown-formatted text
reporter	string	Username of creator	No	john_doe
assignee	string	Assigned user	No	jane_smith
created_on	ISO 8601	Creation timestamp	Yes	2023-06-15T10:30:00Z
updated_on	ISO 8601	Last modification timestamp	No	2024-01-20T14:00:00Z
comment_count	integer	Number of associated comments	No	7
comments (array)	array	Nested or separate comment objects	No	Array of comment objects
comments[].id	integer	Comment identifier	Yes*	101
comments[].issue	integer	Parent issue ID for joining	Yes*	42
comments[].content	string	Comment body text	No	Plain or markdown text
comments[].user	string	Comment author	No	contributor_x
comments[].created_on	ISO 8601	Comment timestamp	No	2023-06-16T08:00:00Z
component	string	Project component label	No	backend, frontend, api
milestone	string	Target milestone or version	No	v2.1.0
version	string	Affected software version	No	v1.9.3
votes	integer	Community vote count	No	12
watchers	integer	Number of watchers	No	5

Frequently Asked Questions

The tool expects Bitbucket Cloud's export format (version 1.0). The root object should contain arrays keyed as issues and comments (or comments nested within each issue object). Each issue must have at minimum an id, title, status, and created_on field. If your export uses a different root key (e.g., the entire file is a flat array), the tool attempts auto-detection by scanning for objects containing id and title properties.

Bitbucket exports often separate issues and comments into distinct arrays. The converter performs an in-memory join by matching each comment's issue field (an integer foreign key) against each issue's id. Comments with no matching issue ID are collected into an "orphaned comments" section at the end of the output. This join has O(n + m) complexity using a hash map lookup.

No. The generated HTML file is entirely self-contained. All CSS styles are embedded inline within a <style> tag. No external fonts, scripts, or CDN resources are referenced. The file renders correctly when opened from a local filesystem in any modern browser.

All user-generated content fields (title, body, comments) pass through HTML entity escaping before rendering. Characters <, >, &, and " are replaced with their entity equivalents. This prevents XSS injection in the output file. After escaping, basic Bitbucket markup patterns (bold with ** and italic with *) are converted to safe HTML tags.

The tool enforces a 50 MB client-side limit. Bitbucket exports for repositories with fewer than 10,000 issues typically fall well under this. Beyond 50 MB, the browser's JSON parser may run into memory constraints. For very large exports, consider splitting the JSON file by issue ID ranges before processing.

Yes. After uploading, the tool displays filter controls for status (open, resolved, closed, on hold, invalid, duplicate, wontfix), kind (bug, enhancement, proposal, task), and priority (trivial through blocker). Only issues matching active filters are included in the generated HTML file and the in-page preview.

Missing optional fields (assignee, component, milestone, version) render as an em-dash ( - ) in the output. Missing required fields trigger a validation warning in the toast notification area but do not halt processing. Issues without a title default to "Untitled Issue #[id]". Null comment content renders as "[empty comment]".