Convert TEXTILE to JIRA
Turn TEXTILE files into JIRA. Jira wiki markup with headings, lists, tables and links.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TEXTILE files on the dialor turn it to pick what to do
Textile text ready for a Jira issue.Headings, lists, tables and links come over as Jira wiki markup.
What you get
One file of Jira wiki markup, the syntax used in Jira issue descriptions. Headings, lists, tables and links in the Textile source are written in their Jira form.
Line breaks inside a paragraph stay as they are, the same way Textile treats them. A paragraph written over several lines keeps those lines.
What changes or is left behind
Cell spans in tables are not kept. A cell that spans several columns or rows in Textile does not span them in the Jira output.
Images stay as links. They are not embedded as pictures in the output.
Options
This conversion has no options. Each Textile file becomes one Jira file as it is.
To go the other way, use JIRA to TEXTILE.
TEXTILE and JIRA.What each format is.
The formats
Textile
Textile markup, once common in Rails apps and Redmine.
- Extensions
- .textile
- MIME type
- text
/x -textile - Kind
- Text and data
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 TEXTILE to JIRA conversion through the API, for your app or your agent.
$ cv convert report.textile report.jira$ cv convert report.textile report.jiraQuestions.What people ask about TEXTILE to JIRA.
Yes. Headings and lists are written as Jira wiki markup, along with tables and links.
Every line break is kept, as Textile does. Lines in a paragraph are not joined together.
Images stay as links. They are not turned into embedded pictures.
No. Cell spans are not kept, so a merged cell does not span columns or rows in the Jira output.