Convert JIRA to Wiki

Why Convert JIRA to Wiki?

Converting JIRA markup to Wiki markup enables you to migrate project documentation from Atlassian Confluence to MediaWiki-based platforms. Both are wiki systems, but they use different markup syntaxes. This conversion bridges the gap, allowing teams to move their content between these ecosystems while preserving formatting and structure.

MediaWiki powers Wikipedia and thousands of corporate knowledge bases worldwide. Converting Jira content to Wiki markup allows you to publish technical documentation, project specifications, and team knowledge on these widely accessible platforms. Wiki markup supports internal linking with [[page names]], categories for organization, and templates for consistent formatting.

Teams transitioning from Atlassian Confluence to a self-hosted MediaWiki instance can use this conversion to bulk-migrate their documentation. The converted Wiki markup preserves headings, tables, lists, and links from the original Jira content, reducing the manual effort needed during migration.

Key Benefits of Converting JIRA to Wiki:

• Platform Migration: Move documentation from Confluence to MediaWiki
• Internal Linking: Use [[wiki links]] to connect related pages
• Category Support: Organize content with [[Category:Topic]] tags
• Template System: Apply consistent formatting with {{templates}}
• Revision History: Built-in version tracking for all content changes
• Open Platform: MediaWiki is free and open-source
• Community Proven: Same technology powering Wikipedia

Practical Examples

Example 1: Issue Documentation to Wiki

Input JIRA file (doc.jira):

h1. API Reference

h2. Authentication
The API uses *OAuth 2.0* for authentication. See the [Authentication Guide|https://docs.example.com/auth] for details.

h3. Endpoints
||Method||Endpoint||Description||
|GET|/api/users|List all users|
|POST|/api/users|Create a user|
|DELETE|/api/users/:id|Delete a user|

{code:bash}
curl -H "Authorization: Bearer TOKEN" https://api.example.com/users
{code}

Output Wiki file (doc.wiki):

= API Reference =

== Authentication ==
The API uses '''OAuth 2.0''' for authentication. See the [https://docs.example.com/auth Authentication Guide] for details.

=== Endpoints ===
{| class="wikitable"
|-
! Method !! Endpoint !! Description
|-
| GET || /api/users || List all users
|-
| POST || /api/users || Create a user
|-
| DELETE || /api/users/:id || Delete a user
|}

<pre>
curl -H "Authorization: Bearer TOKEN" https://api.example.com/users
</pre>

Example 2: Project Page to Wiki

Input JIRA file (project.jira):

h1. MyApp Project

h2. Overview
MyApp is a _cloud-native_ application for *data processing*.

h2. Architecture
* Frontend: React with TypeScript
* Backend: Python with Django
* Database: PostgreSQL
* Cache: Redis

h2. Team
||Name||Role||Contact||
|Alice|Tech Lead|[email protected]|
|Bob|Backend Developer|[email protected]|
|Charlie|Frontend Developer|[email protected]|

Output Wiki file (project.wiki):

= MyApp Project =

== Overview ==
MyApp is a ''cloud-native'' application for '''data processing'''.

== Architecture ==
* Frontend: React with TypeScript
* Backend: Python with Django
* Database: PostgreSQL
* Cache: Redis

== Team ==
{| class="wikitable"
|-
! Name !! Role !! Contact
|-
| Alice || Tech Lead || [email protected]
|-
| Bob || Backend Developer || [email protected]
|-
| Charlie || Frontend Developer || [email protected]
|}

[[Category:Projects]]
[[Category:Software Development]]

Example 3: Knowledge Base Article to Wiki

Input JIRA file (kb.jira):

h2. Troubleshooting Guide

h3. Common Errors

*Error 500:* Internal server error. Check the _application logs_ for details.

{quote}
If the error persists after restarting, contact the DevOps team via [Support Channel|https://chat.example.com/support].
{quote}

h3. Recovery Steps
# Stop the application service
# Clear the cache directory
# Restart the database
# Start the application service
# Verify health check endpoint

Output Wiki file (kb.wiki):

== Troubleshooting Guide ==

=== Common Errors ===

'''Error 500:''' Internal server error. Check the ''application logs'' for details.

<blockquote>
If the error persists after restarting, contact the DevOps team via [https://chat.example.com/support Support Channel].
</blockquote>

=== Recovery Steps ===
# Stop the application service
# Clear the cache directory
# Restart the database
# Start the application service
# Verify health check endpoint

[[Category:Troubleshooting]]

Frequently Asked Questions (FAQ)

Q: How are Jira headings mapped to Wiki headings?

A: Jira h1. maps to Wiki = Heading = (single equals), h2. to == Heading == (double equals), and so on through h6. which maps to ====== Heading ====== (six equals signs).

Q: How is text formatting converted?

A: Jira *bold* converts to Wiki '''bold''' (triple apostrophes), and Jira _italic_ converts to Wiki ''italic'' (double apostrophes). Strikethrough uses <s> tags in Wiki markup.

Q: How are Jira tables converted to Wiki tables?

A: Jira tables with ||header|| and |cell| syntax are converted to MediaWiki table syntax using {| class="wikitable" ... |}. Headers use ! markers and data cells use | markers with |- row separators.

Q: How are Jira links converted to Wiki links?

A: Jira external links [text|url] are converted to Wiki format [url text]. For internal wiki pages, you can manually convert these to [[Page Name|display text]] format after conversion.

Q: Can I add Wiki categories after conversion?

A: Yes, after conversion you can add category tags like [[Category:Topic]] at the bottom of the Wiki markup. This integrates the converted content into your wiki's category system.

Q: How are Jira code blocks handled?

A: Jira {code}...{code} blocks are converted to Wiki <pre>...</pre> or <syntaxhighlight> tags. If the Jira code block specifies a language, the syntaxhighlight tag includes the lang attribute.

Q: Can I use Wiki templates with the converted content?

A: Yes, you can add Wiki templates ({{template_name}}) to the converted markup. Templates are processed by the MediaWiki engine and can add standardized infoboxes, navigation, or formatting.

Q: Is the output compatible with all MediaWiki installations?

A: Yes, the generated Wiki markup uses standard MediaWiki syntax compatible with all MediaWiki installations, including Wikipedia, Fandom wikis, and self-hosted instances. Basic formatting works universally across all MediaWiki versions.