Convert JIRA to MediaWiki

Why Convert JIRA to MediaWiki?

Converting Jira markup to MediaWiki format enables you to transfer project documentation from Atlassian tools to MediaWiki-powered wikis such as Wikipedia, corporate wikis, and knowledge bases. Both formats share similar concepts but use different syntax.

MediaWiki's powerful markup system supports advanced features like templates, categories, and complex table layouts that can enhance your documentation. By converting Jira content, you can leverage these wiki-native features for better content organization and discoverability.

This conversion is particularly valuable for organizations migrating from Atlassian Confluence to MediaWiki, or for teams that need to publish their Jira project documentation on internal wiki platforms for broader organizational access.

Key Benefits of Converting JIRA to MediaWiki:

• Wiki Publishing: Publish Jira content on any MediaWiki-powered wiki
• Template System: Leverage MediaWiki's powerful template and transclusion features
• Category Organization: Organize content with MediaWiki categories and namespaces
• Collaborative Editing: Enable wiki-style collaborative content editing
• Revision History: Benefit from built-in version tracking and diff viewing
• Cross-Linking: Create internal wiki links between related pages
• Wide Adoption: MediaWiki powers Wikipedia and thousands of organizational wikis

Practical Examples

Example 1: Technical Documentation to MediaWiki

Input JIRA file (docs.jira):

h1. API Authentication Guide

h2. Overview
The API uses *OAuth 2.0* for authentication.
All requests must include a valid _access token_.

h2. Supported Methods
* Bearer token authentication
* API key authentication
* Client credentials flow

{code:python}
import requests

headers = {"Authorization": "Bearer YOUR_TOKEN"}
response = requests.get("https://api.example.com/data", headers=headers)
{code}

Output MediaWiki file (docs.mediawiki):

= API Authentication Guide =

== Overview ==
The API uses '''OAuth 2.0''' for authentication.
All requests must include a valid ''access token''.

== Supported Methods ==
* Bearer token authentication
* API key authentication
* Client credentials flow

<syntaxhighlight lang="python">
import requests

headers = {"Authorization": "Bearer YOUR_TOKEN"}
response = requests.get("https://api.example.com/data", headers=headers)
</syntaxhighlight>

Example 2: Status Table to MediaWiki

Input JIRA file (status.jira):

h2. Component Status

||Component||Version||Status||Owner||
|Frontend|3.2.1|Stable|Team Alpha|
|Backend API|2.8.0|Beta|Team Bravo|
|Database|5.0.3|Stable|Team Charlie|

{panel:title=Next Release}
Version 4.0 is planned for *Q2 2026*.
{panel}

Output MediaWiki file (status.mediawiki):

== Component Status ==

{| class="wikitable"
! Component !! Version !! Status !! Owner
|-
| Frontend || 3.2.1 || Stable || Team Alpha
|-
| Backend API || 2.8.0 || Beta || Team Bravo
|-
| Database || 5.0.3 || Stable || Team Charlie
|}

{{Notice|title=Next Release|text=Version 4.0 is planned for '''Q2 2026'''.}}

Example 3: Process Documentation to MediaWiki

Input JIRA file (process.jira):

h1. Deployment Process

h2. Prerequisites
# Verify all tests pass
# Get approval from _tech lead_
# Ensure *staging* environment is green

h2. Steps
# Merge feature branch to main
# Wait for CI/CD pipeline
# Verify deployment on staging
# Promote to production

{quote}
Always perform deployments during low-traffic hours.
{quote}

For more details, see [Runbook|https://wiki.example.com/runbook].

Output MediaWiki file (process.mediawiki):

= Deployment Process =

== Prerequisites ==
# Verify all tests pass
# Get approval from ''tech lead''
# Ensure '''staging''' environment is green

== Steps ==
# Merge feature branch to main
# Wait for CI/CD pipeline
# Verify deployment on staging
# Promote to production

<blockquote>
Always perform deployments during low-traffic hours.
</blockquote>

For more details, see [https://wiki.example.com/runbook Runbook].

Frequently Asked Questions (FAQ)

Q: How do Jira and MediaWiki heading syntax differ?

A: Jira uses h1. through h6. prefixes, while MediaWiki uses equals signs: = Heading 1 =, == Heading 2 ==, and so on. The converter maps each Jira heading level to the corresponding MediaWiki heading syntax.

Q: How are Jira tables converted to MediaWiki tables?

A: Jira tables using ||header|| and |cell| syntax are converted to MediaWiki's table markup using {| class="wikitable", ! for headers, |- for row separators, and | for cells. The resulting tables render properly on any MediaWiki installation.

Q: Are code blocks supported in the conversion?

A: Yes. Jira {code:language}...{code} blocks are converted to MediaWiki <syntaxhighlight lang="language"> tags, which provide syntax highlighting on MediaWiki sites with the SyntaxHighlight extension installed.

Q: How are Jira links converted to MediaWiki links?

A: Jira external links [text|url] are converted to MediaWiki external link syntax [url text]. Internal wiki links can be manually adjusted to use [[Page Name]] syntax after conversion.

Q: What happens to bold and italic formatting?

A: Jira bold (*text*) becomes MediaWiki bold ('''text'''), and Jira italic (_text_) becomes MediaWiki italic (''text''). Both formats use apostrophe-based syntax, just with different conventions.

Q: Can I use the output directly on Wikipedia?

A: The output uses valid MediaWiki syntax compatible with Wikipedia and all MediaWiki installations. However, Wikipedia has specific content guidelines and notability requirements that must be met independently of the markup format.

Q: How are Jira panels converted?

A: Jira {panel} blocks are converted to MediaWiki notice or message box templates, preserving the title and content. The exact template name may vary depending on your wiki's installed templates.

Q: Are Jira lists compatible with MediaWiki?

A: Yes. Both Jira and MediaWiki use similar list syntax: * for bulleted lists and # for numbered lists. The conversion preserves the list structure, including nested lists using ** and ## patterns.