Convert POD to JIRA

Turn POD files into JIRA. Jira wiki markup with headings, lists, tables and links.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop POD files on the dialor turn it to pick what to do

Perl docs, ready for a Jira issue.Headings, lists, tables and links come across as Jira wiki markup.

  1. What you get

    One JIRA file with the structure of the POD document. Headings, lists, tables and links are written in Jira wiki markup, so you can paste the text into a Jira issue description.

    Verbatim paragraphs, the indented code blocks in a POD file, become code in the output.

  2. What changes or is dropped

    Links to other manual pages keep only their name. The link target is not carried over.

    Paragraphs marked with =for comment are dropped. Blocks opened with =begin for HTML pass through only where HTML can be kept.

  3. Related conversions

    See every POD conversion for the other formats POD converts to, or every JIRA conversion for the other ways to produce Jira markup.

POD and JIRA.What each format is.

The formats

From · POD

Perl POD

Plain Old Documentation, the markup of Perl manuals and module docs.

Extensions
.pod
MIME type
text/x-pod
Kind
Text and data
To · JIRA

Jira Wiki Markup

Jira wiki markup, the syntax of Jira issue descriptions.

Extensions
.jira
MIME type
text/x-jira
Kind
Text and data

In your code.The same POD to JIRA conversion through the API, for your app or your agent.

terminal
$ cv convert report.pod report.jira
$ cv convert report.pod report.jira

Questions.What people ask about POD to JIRA.

01OF 04

Jira wiki markup with headings, lists, tables and links. It is the syntax used in Jira issue descriptions.

Verbatim paragraphs become code in the Jira markup.

No. Paragraphs marked with =for comment are dropped.

They keep only their name. The rest of the link is not kept.

More conversions.Other ways in and out of POD and JIRA.