Have something to say?

Tell us how we could make the product more useful to you.

Aki Planned Time vs Clickup Estimated Time

On ClickUp, I put time estimates on the top-level tasks based on what was quoted to clients. When ClickUp syncs my tasks to Aki, Aki sets the estimated time as the planned time. Which makes sense, objectively, but I don’t often work on the tasks in one sitting because there will be a long list of subtasks. When I plan a task in the calendar, I may only be planning it for 2 hours that day, instead of the total 6 estimated hours, for example. I would be fine to sort this out manually by duplicating the task or something, but the problem is that it then changes the estimated time on ClickUp to the 2 hours planned. If we could choose to sync the Aki planned time to the ClickUp time tracked instead, that would be great! Or just turn off the time syncing all together, and handle it manually. Or, if Aki pulled in the subtasks, not just the top level task from ClickUp, then I could put more realistic/accurate time estimates on the subtasks, and the planned time would line up more reasonably.

Relly About 12 hours ago

Add “Time Horizon” grouping to Project List views (This Week / Next Week / This Month / Next Month / Someday)

Akiflow already uses a time-horizon grouping system (This Week / Next Week / This Month / Next Month / Someday) across its main task views. I’d like this same grouping available as an option in Project List views. Current behaviour: Project tasks display as a flat list. The only way to add structure is manually creating sections and dragging tasks in, which goes stale as dates change. Requested behaviour: A “Group by: Time Horizon” toggle in Project List views that automatically buckets tasks using the same logic already applied elsewhere in the app. This would make project views as planning-friendly as the main planner - using logic that’s already built into the product.​​​​​​​​​​​​​​​​

Elias 8 days ago

2

Allow selecting a non-default Google Calendar when creating events with Aki

Description Users would like the ability to choose which calendar to use when creating events with Aki, especially when multiple calendars exist under the same Google account. Currently, even when specifying a different calendar, events are always created in the default calendar, forcing users to manually change the calendar afterward. Use case Many users manage multiple calendars (e.g., Work, Personal, Shared, Projects) within the same Google account. When creating events through Aki, they need to assign the event to a specific calendar, not always the default one. Current behavior Aki creates the event in the default Google Calendar Specifying another calendar does not persist User must manually move the event after creation Expected behavior Ability to select the target calendar when creating the event Option to set a different default calendar for Aki Aki should respect the selected calendar when the user specifies one Impact Medium — does not block usage, but creates friction for users who manage multiple calendars and schedule frequently.

Kevin 14 days ago

1