Convert JIRA to TSV
Max file size 100mb.
JIRA vs TSV Format Comparison
| Aspect | JIRA (Source Format) | TSV (Target Format) |
|---|---|---|
| Format Overview |
JIRA
Jira Markup Language
JIRA markup is Atlassian's text formatting language used across Jira, Confluence, and Bitbucket. It provides a lightweight syntax for bold, italic, headings, tables, code blocks, lists, and links without requiring HTML knowledge. The format is designed for quick issue descriptions and project documentation. Markup Language Atlassian |
TSV
Tab-Separated Values
TSV is a simple tabular data format where each line represents a row and columns are separated by tab characters. TSV is widely used for data exchange between spreadsheet applications, databases, and data processing tools. Its simplicity makes it ideal for clean data that does not contain tab characters. Tabular Data Plain Text |
| Technical Specifications |
Structure: Plain text with Jira markup syntax
Encoding: UTF-8 Format: Atlassian markup language Platforms: Jira, Confluence, Bitbucket Extensions: .jira, .txt |
Structure: Tab-delimited rows and columns
Encoding: UTF-8, ASCII, or locale-specific Standard: IANA MIME type text/tab-separated-values MIME Type: text/tab-separated-values Extension: .tsv, .tab |
| Syntax Examples |
JIRA uses Atlassian wiki markup: h1. Main Heading
*bold text* and _italic text_
||Header 1||Header 2||
|Cell A1|Cell A2|
|Cell B1|Cell B2|
{code:java}
System.out.println("Hello");
{code}
|
TSV uses tab characters as column delimiters: Name Age City Alice 30 New York Bob 25 London Charlie 35 Tokyo |
| Content Support |
|
|
| Advantages |
|
|
| Disadvantages |
|
|
| Common Uses |
|
|
| Best For |
|
|
| Version History |
Introduced: 2002 (Atlassian)
Current Version: Jira Cloud markup Status: Active, widely used in enterprise Evolution: Wiki markup to rich text editor (markup still supported) |
Introduced: Early computing era (no formal date)
Current Version: IANA MIME type text/tab-separated-values Status: Active, widely used in data exchange Evolution: Simple tab delimiter standard, unchanged since inception |
| Software Support |
Primary: Jira, Confluence, Bitbucket
Editors: Any text editor Converters: Pandoc (jira format), j2m Platforms: Atlassian Cloud, Data Center, Server |
Spreadsheets: Excel, Google Sheets, LibreOffice Calc
Languages: Python (csv module), R, awk, Perl Databases: MySQL LOAD DATA, PostgreSQL COPY Tools: cut, paste, sort (Unix commands) |
Why Convert JIRA to TSV?
Converting JIRA markup to TSV extracts tabular data from Jira tables into a format that can be immediately opened in Excel, Google Sheets, or any spreadsheet application. This is invaluable when you need to analyze project data, create reports, or import Jira content into databases and data processing tools.
Jira issues often contain tables with metrics, status updates, and tracking data that teams need to analyze in spreadsheets. Converting these tables to TSV provides a clean, tab-separated format that preserves column structure and can be pasted directly into any spreadsheet application without import configuration.
TSV is preferred over CSV in many scientific and data processing contexts because it avoids the complexity of comma escaping in text fields. When Jira content contains commas (which is common in descriptions), TSV provides a cleaner extraction format without quoting ambiguity.
Key Benefits of Converting JIRA to TSV:
- Spreadsheet Ready: Open directly in Excel, Google Sheets, LibreOffice
- Data Extraction: Extract structured table data from Jira content
- No Quoting Issues: Tab separation avoids CSV comma-quoting complexity
- Database Import: Load data directly into databases with bulk import
- Data Analysis: Process extracted data with Python, R, or Unix tools
- Clean Format: Simple structure for programmatic processing
- Clipboard Compatible: Copy-paste into spreadsheets preserves columns
Practical Examples
Example 1: Issue Tracking Table to TSV
Input JIRA file (issues.jira):
h2. Sprint Backlog ||Issue||Summary||Priority||Status||Assignee|| |PROJ-101|Fix login timeout|Critical|In Progress|Alice| |PROJ-102|Update dashboard UI|Medium|To Do|Bob| |PROJ-103|Add export feature|High|Done|Charlie| |PROJ-104|Improve search speed|High|In Progress|Alice|
Output TSV file (issues.tsv):
Issue Summary Priority Status Assignee PROJ-101 Fix login timeout Critical In Progress Alice PROJ-102 Update dashboard UI Medium To Do Bob PROJ-103 Add export feature High Done Charlie PROJ-104 Improve search speed High In Progress Alice
Example 2: Test Results to TSV
Input JIRA file (tests.jira):
h3. Test Execution Results *Sprint:* 15 *Date:* 2025-12-01 ||Test Case||Module||Result||Duration|| |TC-001|Authentication|Pass|1.2s| |TC-002|User Profile|Pass|0.8s| |TC-003|Payment|Fail|3.5s| |TC-004|Search|Pass|0.5s| |TC-005|Export|Skip|0.0s|
Output TSV file (tests.tsv):
Test Case Module Result Duration TC-001 Authentication Pass 1.2s TC-002 User Profile Pass 0.8s TC-003 Payment Fail 3.5s TC-004 Search Pass 0.5s TC-005 Export Skip 0.0s
Example 3: Resource Allocation to TSV
Input JIRA file (resources.jira):
h2. Team Resource Allocation
||Team Member||Project||Allocation||Start Date||End Date||
|Alice|Backend API|100%|2025-10-01|2025-12-31|
|Bob|Frontend UI|75%|2025-10-15|2026-01-15|
|Charlie|DevOps|50%|2025-11-01|2025-12-31|
{panel:title=Note}
Allocations are _reviewed monthly_ and adjusted based on *project priorities*.
{panel}
Output TSV file (resources.tsv):
Team Member Project Allocation Start Date End Date Alice Backend API 100% 2025-10-01 2025-12-31 Bob Frontend UI 75% 2025-10-15 2026-01-15 Charlie DevOps 50% 2025-11-01 2025-12-31
Frequently Asked Questions (FAQ)
Q: Which Jira content is extracted into TSV?
A: The converter primarily extracts Jira tables (||header|| and |cell| syntax) into TSV format. Each table row becomes a TSV line with tab-separated fields. Non-tabular content like headings and paragraphs is not included in the TSV output.
Q: Can I open TSV files in Excel?
A: Yes, Microsoft Excel, Google Sheets, and LibreOffice Calc all support TSV files. You can open them directly or use the import wizard to ensure correct column separation. Most applications auto-detect tab delimiters.
Q: What is the difference between TSV and CSV?
A: TSV uses tab characters to separate fields, while CSV uses commas. TSV is simpler because it does not require quoting rules for fields containing commas. TSV is preferred when data values commonly contain commas.
Q: How are Jira formatting markers handled in TSV?
A: Jira formatting markers like *bold*, _italic_, and {code} are stripped from the TSV output. Only the plain text content of each cell is included, ensuring clean data for analysis and processing.
Q: Can I import TSV data into a database?
A: Yes, most databases support TSV bulk import. MySQL uses LOAD DATA INFILE with FIELDS TERMINATED BY '\t', and PostgreSQL uses the COPY command with DELIMITER E'\t'. This is efficient for importing Jira table data.
Q: How are multiple Jira tables handled?
A: If the Jira file contains multiple tables, they are extracted sequentially with an empty line between each table in the TSV output. Each table retains its own header row for clarity.
Q: What happens to non-table content in the Jira file?
A: Non-tabular content (headings, paragraphs, lists, code blocks) is converted to a single-column text representation in the TSV output. The primary focus is extracting structured table data.
Q: Can I process TSV files with Python?
A: Yes, Python's csv module supports TSV by setting delimiter='\t'. You can also use pandas with pd.read_csv('file.tsv', sep='\t') for powerful data analysis and manipulation of the extracted data.