Skip to content

Add MarkdownJiraConverter package#9338

Open
crqcastro wants to merge 1 commit intosublimehq:masterfrom
crqcastro:master
Open

Add MarkdownJiraConverter package#9338
crqcastro wants to merge 1 commit intosublimehq:masterfrom
crqcastro:master

Conversation

@crqcastro
Copy link
Copy Markdown

@crqcastro crqcastro commented Mar 18, 2026

  • I'm the package's author and/or maintainer.
  • I have read [the docs][1].
  • I have tagged a release with a [semver][2] version number.
  • My package repo has a description and a README describing what it's for and how to use it.
  • My package doesn't add context menu entries. *
  • My package doesn't add key bindings. **
  • Any commands are available via the command palette.
  • Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
  • If my package is a syntax it doesn't also add a color scheme. ***
  • I use [.gitattributes][3] to exclude files from the package: images, test files, sublime-project/workspace.

My package is a Markdown ↔ Jira converter for Sublime Text.

It allows developers to quickly convert between Markdown and Jira text formatting, supporting common elements such as headings, lists (including nested), code blocks, inline code, tables, links, images and blockquotes.

There are similar tools available outside Sublime Text or limited to one-way conversion. However, this package provides:

  • bidirectional conversion (Markdown → Jira and Jira → Markdown)
  • support for selection or entire file
  • clipboard-only conversion commands
  • configurable behavior via settings
  • integration with the command palette and Tools menu

This makes it particularly useful for developers who frequently work between documentation (Markdown) and issue tracking (Jira), improving productivity and reducing manual formatting work.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 8, 2026

Package Review

Channel Diff

Removed (none), changed (none), added (none).

Result

No changed or added packages to review.

@braver
Copy link
Copy Markdown
Collaborator

braver commented Apr 8, 2026

Please add your entry to the m.json file, and match the other entries there in terms of formatting and information.

As for your package itself:

  • Your settings and keybindings go in the package settings menu along with those of other packages. It's fine to leave the other functionality in the tools menu.
  • It's also common practice to expose settings and keybindings via the command palette (search for "Preferences: " in the palette for examples).
  • Be sure to opt-in to the newer python 3.8 package runtime (example).
  • You probably want to remove and ignore the .DS_Store file.

@braver braver added the feedback provided The changes and package have been seen by a reviewer label Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feedback provided The changes and package have been seen by a reviewer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants