Chrome extension for sending JIRA tickets to OmniFocus
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Chrome extension for sending JIRA tickets to OmniFocus.

Travis CI status
bitHound Overall Score bitHound Dependencies bitHound Dev Dependencies bitHound Code
Scrutinizer status

This extension adds a big, lovely "Send to OmniFocus" button atop the right column of the JIRA ticket page. Click that button to quickly send a JIRA ticket into OmniFocus. The extension also supports Mail Drop, so you can send items to your OmniFocus Inbox even if you haven't got OmniFocus installed on this computer. (Yes, even from Linux or Windows.)

Use it allocate today's work. Use it to remember to follow up on some ticket, even one that's not yours (let's face it: merely being a watcher isn't all that useful when you've got a mountain of things you're responsible for).

Most importantly, use it to Get Things Done.

NOTE: I am not in any way affiliated with Omnigroup (the folks who make OmniFocus), or with Atlassian (the folks that make JIRA). Neither the Omnigroup nor Atlassian endorse this extension in any way, express nor implied. They don't even know who I am.

Getting Started

After cloning this project to your computer, you'll need to build the extension.

$ npm install
$ npm run build

Known Limitations

At this time, this extension only works its magic from the ticket detail page. That is to say that it doesn't work from any quick-edit / AJAX-overlay views of ticket information (ie, from the Kanban board, etc).


I enjoy maintaining this extension, and am happy that there are folks out there using it. I'm always thrilled to receive feedback, feature requests, and even PRs. If you've got a feature to request or a bug to report, please file an issue on Github.

If you're a little more technically inclined, and would like to submit a pull request, please note that I have implemented ESLint configs (based on the Airbnb JS Styleguide) for the project that code submitted in PRs must honor (I've configured Hound CI to automatically decline any PRs that fail to validate according to the project's configured linting rules). You can minimize the chances of encountering an auto decline by ensuring that you've run npm run lint on your changes before submitting the pull request. I can also recommend installing the appropriate modules for both ESLint and EditorConfig for whatever editor / IDE you like to use for development.