Jira and Omnifocus

Hello Guys,

Since the absence of a simple way to synchronize Jira with OmniFocus, I created a native Sync Plugin, which works without complicate requirements.

Looking forward to getting some feedback about bugs and about my implementation. It currently works the way I need it for my projects. All Details here:

Regards Bastian

2 Likes

Greetings! Great idea, and thank you for sharing with the Automation community. I’m sure this project will inspire fellow Omni Automation enthusiasts. Also, glad that the new Fetch APIs are working for you.

A couple small issues:

  1. The plug-in is using an older template design where the action was stored in the _ var. New design uses self-invoking anonymous function like the example shown below.

  2. Since the plug-in is only targeting OmniFocus (and not other Omni apps as well), you can use the app-specific file extension of “omnifocusjs” which will cause the plug-in to adopt the proper OmniFocus plug-in icon and trigger the installation process when the plug-in file is opened.

     (() => {
     	var action = new PlugIn.Action(function(selection, sender){
     		// action processing code goes here
     	});
     	
     	action.validate = function(selection, sender){
     		// perform any status checks and returns a boolean value
     		return true
     	};
    
     	return action;
     })();
    

Cheers!

Thank you @Sal

Updated the File Extension and the Template design.

Some Updates:

  1. The JavaScript Programmer Martin Joly helped me and made the code JavaScript Style and not Python Style any more ;)
  2. The Plugin has now the option, to add all Jira Ticket Comments as Subtask to the Task (for me a perfect)
  3. The Plugin now supports multiple Jira instances.

Cool. I can’t wait until I have time to try this out.

Does it support OAUTH or am I going to still have to figure that out for myself?

Nope Sorry, currently only AuthBasic with Password or API Key.
Don’t have the need for OAUTH currently, but I’m open for contributions.

I suspected as much. When/if I get to this, I fully expect to share any OAUTH updates back to you in a pull request.

I can not find any notation about what the URL needs to be and I am concerned this is the reason this script is not working for me.

I am getting this on the console:

NOTICE: Synced https://___.atlassian.net/jira/software/projects/___/boards/1. Checked 0 Tickets, Created 0 new tasks, Added 0 Subtickets for Comments

The edits I made:
(() => {
const action = new PlugIn.Action(function (selection, sender) {
// START EDIT
const configs = [{
user: “email address used”, // use email address for jira cloud
password: “api key used”, // you can use api tokens, see https://id.atlassian.com/manage-profile/security/api-tokens
jiraUrl: “https://.atlassian.net/jira/software/projects//boards/1”,
omnifocusTagToUse: “Jira”, // you can also use the format “Parent1 : Parent2 : Child”
jiraQuery: “assignee=currentuser() and resolution is empty”,
processComments: false, // if true, a subtask is added for each ticket comment
omnifocusCommentTagToUse: “Jira-Comment”,
// },
// {
// user: “”,
// password: “”,
// jiraUrl: “”,
// omnifocusTagToUse: “”,
// jiraQuery: “assignee=currentuser() and resolution is empty”,
// processComments: false,
// omnifocusCommentTagToUse: “”,
//
}]
// END EDIT

Hello Anthonii,

You don’t need the URL to the board, just the base URL of the instance, so the URL with the main folder where Jira is in.

For the instances I work with, its https://jira.domain.de/ and in another case https://domain.de/jia since there it’s in a folder instead a subdomain.

From the Base URL you give, the script needs to reach /api/rest/2

1 Like

Thank you, in my region I had to use the following. https://domain.atlassian.net My next question is, can I have these imported into a specific folder/project directly?

Not yet, but I’m thinking already about a concept to build it. Problem: I sync with more than one instance, so how can I make sure to not miss a new ticket direct after a sync without clicking through the Projects.

Don’t want to use an extra view for that instead the inbox. But will come somehow :)

1 Like

I do ask, but there is something magical that comes when I process my inbox. It is certainly not necessary.