Logseq Jira Plugin

I think I know another scenario why you might be facing this issue.

Does this happen when you type the issue key, and right after that, use the / command? It seems like the block content doesn’t update immediately, so the plugin won’t get the correct contents until much after…

Thanks for creating this!

I have no idea if this is possible with Logseq/Jira, but I am making each Issue a task in Logseq, would be cool to have 3 things:

  1. Automatically add a task designation when you add an Issue to Logseq NOW appended in front.
  2. If the Task gets checked as complete in Logseq, then mark complete in Jira.
  3. Pull in all issues Assigned to me from Jira into a page as separate blocks with marked as tasks in Logseq.

I love the idea and aspiration behind this.

Essentially get your tasks in Logseq, get it done and mark it done within Logseq, and not care about interacting with Jira (which I personally find ancient and slow).

It’s technically feasible for sure.

The workflow would probably be something like.

  • One command/dataview query to pull in all Jira tickets assigned to you.
  • Each ticket becomes a task with the usual TODO DOING and DONE mapped to statusCategories in Jira.
  • When you move it from TODO to DOING, it becomes “IN PROGRESS” in Jira, and when you mark it DONE, it moves to “DONE”.

Does that reasonably map to how you picture the workflow?

2 Likes

Exactly that. Yes, that would be an idea situation.

Hey guys.

Yet to get the workflow process going on Logseq-Jira, (don’t worry @Brad_Nickel, we’ll get there soon).

However, latest updates:

  • Experimental support for automatically refreshing JIRA links.
  • Run a JQL to add all resulting tickets as children blocks (looking for feedback)
  • Support for both Basic Auth and Personal Access Tokens.
  • Support for On-premise version of Jira (thanks to everyone who helped)
  • Code refactoring, clean ups.

Would love to get feedback and how you’re using it.

2 Likes

Just released v0.5.0

  • Support for Org Mode.
2 Likes

I created a couple enhancement requests on github.

  1. Add support for a tags:: property setting a given value. This would really help with queries on project pages.
  2. Add a type:: property to reflect the jira issue type. I work with more than just bugs.

I am currently adding these by hand. Love the plugin and thank you for your work!

1 Like