Jira Integration Config - Simplify & Improve via Filters ॱ◡ॱ
Better for users and for Akiflow. Jira JQL Filters are amazing. The Akiflow integration could be simplified and made exquisitely customizable by making the configuration target a Jira Filter, i.e., https://yourdomain.atlassian.net/issues/?filter=12243 By doing so, there would no longer be a need to select All Issues vs Assigned Issues, which projects, which issue types, et. al., because anything anyone could want can be compactly expressed in the Jira Filter. Atlassian has good documentation and support for these. In the end, I bet this featured implementation will result in a net reduction of lines of code you have to maintain ॱ◡ॱ
Log in to comment and vote
Comments17
[Deleted User]
Nov 2, 2023
This is a big one for me. I'm currently trying to decide between Akiflow and Sunsama and one of Sunsama's advantages is the fact that I can work off of the same query I do in Jira (my open issues in the current sprint ranked by a PM).
[Deleted User]
Feb 24, 2025
Definetly a MUST HAVE, have a filter you can select and autoimport them into the inbox.> with AI they could automatically also be tagged by project if you could relate them to them.
Currently the project by TASK Type is a problem, I may beed around 70 different connectors, as each project has around 7 issue types. and I have over 10 projects I want to monitor in my inbox.
[Deleted User]
Feb 25, 2025
Christian Paredes: That’s a really intricate workflow you’ve got! Appreciate you bumping this and sharing your feedback. Once the team starts working on this, we’ll be sure to keep you updated! 🚀
Frank
Nov 21, 2024
definitely agree this would be a much better approach than what is there now.
Jira gets used a bunch of different ways by different teams and orgs.
Peache
Nov 25, 2024
Frank: Thank you so much for sharing your feedback! We truly appreciate it. Rest assured, we will keep you updated if we work on this!
Josh
Sep 6, 2024
This would be such a simple integration that would make Akiflow MUCH more useful with the Jira integration. Its borderline unusable for me now with the current filters.
Jeson P
Sep 19, 2024
Josh Golosinskiy: We hear you on this. Our product designers will definitely look into this after the current priorities! :)
[Deleted User]
Sep 5, 2024
Must have to make Jira useful for me. Our (many) boards are really complex. Akiflow currently doesn't allow me te configure this (maybe with loads of elbow grease). This is the reason why I'm using Sunsama, even though I dislike that tool 😬
Jeson P
Sep 17, 2024
Maikel Mast: Hopefully this will be added as an added feature of the integration!
[Deleted User]
Jun 9, 2023
Thank you so much for sharing Phil, this is very interesting!
[Deleted User]
Jun 12, 2023
Stefania: Here's a working proof of concept: curl --location --request GET 'https://YOURINSTANCE.atlassian.net/rest/api/2/search?jql=filter=12243' --header 'Content-Type: application/json' --header 'Authorization: Basic YOURAPIKEY' --header 'Cookie: atlassian.xsrf.token=YOURTOKEN' | jq .
Marijn
Jun 4
This is also essential for us. The current filter options do not work for us. We have over 40 projects and 8 issue types per project. My tasks can appear anywhere, so I have to add 40×8 = 320 filters. This is not maintainable.
[Deleted User]
Sep 21
•Merged request
•1 vote
Allow to sync tasks from Jira by filter or JQL query
I want to sync on a specific project only tasks and bugs that have a specific label or where I am the watcher. This way is easier for me to have in my radar “Waiting for” tickets
Akiflow Team
Nov 27, 2025
Hi @Marta García-Obregón Thank you so much for sharing your feedback! We truly appreciate your input.
We will surely notify you once this has been considered and potentially implemented in a future update.
Nancy
Sep 22
•Merged request
•3 votes
Jira Integration: filter by sprints when importing tasks