This is so critical and it is the one thing making me heavily consider not using Akiflow past my trial despite loving a lot of it. Sunsama shows you a substantial amount of ticket data right within their app, so you do not need to leave the app. Context switching is a killer.
Also, there isn’t even an obvious way to to easily get to the Jira issue from Akiflow. You have to dig to find the issue key, but then copying the issue key bewilderingly copies the issue name instead (most of my Jira issues have similar names.)
For me, the title is genuinely the least helpful bit of information. Sunsama is eating Akiflow’s lunch with their Jira integration, please consider this! Jira’s API is very easy to work with, getting the info Sunsama does including a clickable link back to the Jira issue is low hanging fruit.
—
For anyone else who uses Zapier + Akiflow + Jira, my recommendation until this is implemented is to turn off the native integration entirely and instead create a Zap that creates Akiflow tasks based on whatever Jira criteria you need, as you can then pass any of the ticket’s info along as needed. Needing Zapier for this isn’t a great experience though.
Flavio
•
Feb 12
Also, make the ticket details available to Aki!
Akiflow Team
•
Feb 16
Thank you for the suggestion! Importing the full ticket details from Jira, not just the title, is a great idea and would make Akiflow much more useful for managing tasks.
We’ve taken note of this feature request for consideration in future updates.
[Deleted User]
•
Feb 24, 2025
Yes, add description matching JIRA Ticket, this feature is found already on Sunsama and helpy you iunderstand priorities directly instead of switching systems
[Deleted User]
•
Feb 26, 2025
Christian Paredes: Thank you for upvoting and sharing your feedback! We'll keep you updated once the team starts working on this.
Log in to comment and vote
Comments5
James
Oct 8
This is so critical and it is the one thing making me heavily consider not using Akiflow past my trial despite loving a lot of it. Sunsama shows you a substantial amount of ticket data right within their app, so you do not need to leave the app. Context switching is a killer.
Also, there isn’t even an obvious way to to easily get to the Jira issue from Akiflow. You have to dig to find the issue key, but then copying the issue key bewilderingly copies the issue name instead (most of my Jira issues have similar names.)
For me, the title is genuinely the least helpful bit of information. Sunsama is eating Akiflow’s lunch with their Jira integration, please consider this! Jira’s API is very easy to work with, getting the info Sunsama does including a clickable link back to the Jira issue is low hanging fruit.
—
For anyone else who uses Zapier + Akiflow + Jira, my recommendation until this is implemented is to turn off the native integration entirely and instead create a Zap that creates Akiflow tasks based on whatever Jira criteria you need, as you can then pass any of the ticket’s info along as needed. Needing Zapier for this isn’t a great experience though.
Flavio
Feb 12
Also, make the ticket details available to Aki!
Akiflow Team
Feb 16
Thank you for the suggestion! Importing the full ticket details from Jira, not just the title, is a great idea and would make Akiflow much more useful for managing tasks.
We’ve taken note of this feature request for consideration in future updates.
[Deleted User]
Feb 24, 2025
Yes, add description matching JIRA Ticket, this feature is found already on Sunsama and helpy you iunderstand priorities directly instead of switching systems
[Deleted User]
Feb 26, 2025
Christian Paredes: Thank you for upvoting and sharing your feedback! We'll keep you updated once the team starts working on this.