Feature Requests

Subtasks in a checklist need to be able to be assigned to different people. Even if the main task is assigned to one person, it sometimes relies on something first being done by someone else. That does not belong in a separate task, it's all part of the same task, but parts need to be owned by separate people.

Currently, it requires two clicks just to get into the editable date field, then I have to enter a very specific, non-intuitive date format with punctuation (YYYY-MM-DD) or click more times to find and select the date I need in the calendar pop-up. After all that, I still have to click Save. Ideally, Double would pull the reconciled-through date right from QBO. As a backup, I should have the ability to click only once to access the editable date field, then enter the date as a standard MMDDYYYY (or even just MMDD, with the YYYY being automatically filled from current year if it is not typed out) without additional punctuation. This field should then auto-save without an additional button needing to be clicked. Thank you for your consideration!

So I have been training on the task views but one thing that I always get is when they are in the close there is not a big enough divider of the custom tasks and close tasks. I think Custom should be the standard white and the close should be a light purple to show this is the actual month close. (also due dates in order should naturally be a think on all sections and it doesn't happen. really frustrating. Visually the purple outline has helped when hovering over tasks, but its still hard to see the divide and the most mis-understood part of Double that I have to explain more than anything. Having a darker divider could also help but I like having the sections a totally different color to really stand out.

It would be great to add a column to tasks list that shows the date the person before you signed off on the task. This would help to prioritize your sign offs based on when the original sign off was completed. Oldest to newest, etc.

Following up on this feedback, marked as "complete:" https://doublehq.canny.io/feature-requests/p/close-due-dates-select-other-months Despite the previous post being marked as complete, we still cannot set a close due date (or a due date for any of the tasks in that close) beyond the subsequent month. Please, please add this flexibility in close due dates. Would that we could have every monthly close done by the end of the subsequent month, but anyone working with clients knows they do not always respond to us, or provide us needed documents, in such a timely manner.

Would love to see the ability to embed a link within verbiage of text in task notes. For SOPs, sheets, etc. Just nice to be able to have that in one spot with the task in a clean format rather than the whole url cluttering it up.

I can change in the client the close that needs to be worked on however it doesn't stay on that one for workflow and dashboard. So for example if we have a client behind on their books because of a reason I should be able to choose the month we need to work on and have it stay on that month and then in the dashboard everyone can see that instead of having to open all outstanding closes.

It would be great to have the ability to complete sign-offs in bulk from the Task List, in addition to the other requests to create sign-offs in bulk. This would be particularly helpful when cleaning up historical tasks.

Can it be set up so that the time‑stamped balance reflects the balance as of the latest sign‑off instead of the first? This would allow for reviewers to make changes to account reconciliations without undoing the preparers sign-off.

When i have new team members working on a client, I'd want a way to manage the review of those tasks, rather than them marking it as complete. I'd love if it would be possible on a "Per-Client" basis (via a checkbox setting), if we could limit the Prepare to only be able to mark items as "ready for review" and then the "Reviewer" would be the only personal able to mark a task as "Done". I could see the benefits from a QA perspective.