Great minds think alike

I was trying to delete multiple tasks that were set to repeat every year and because of that when I deleted them they were reappearing. Other than removing the checkmark manually on each of the tasks, there's no way to stop them to appear again on your list of tasks.    After you select multiple tasks and then Edit I would suggest simply adding a "Set to Repeat" check or uncheck option with the day's option. This way you can set multiple tasks to either repeat or stop the repetition.  ...read more

When you are in the process of creating follow up tasks I would love to have more added flexibility in defining the follow-up tasks such as assign it to different person or add additional notes to the follow-up tasks directly as the follow up tasks are being created. This would be instead of having to go to the deal, open your newly created task and then manually edit it there. This would add efficiency during the creation of follow-up tasks  ...read more

Our sales team while creating tasks worked a method to use "COMPANY NAME | CLINET SURENAME - shoet taks discription". We would like to use snippet to for it.  Other idea is to make possibility to change defaul name of followup task. Instead of 'Follow up with Krzysztof PAWLAK' we would like to have 'COMTEC 3D | PAWLAK - follow up"    It will speed up our process and make task more userfreindly.       ...read more

currently when creating a task we can see who the task was assigned to, however, even when checking the task history there is no way a user can see who created a task.   This would be a valuable addition for all customers making extensive use of the tasks tool, for example having an additional "created by" field would be great ...read more

The main objective would be to be able to define or change the value of a property of a specific transaction based on a task completion status.    There are multiple ways of doing this but after trying many options, I found that the easiest one would be to have "Activities: properties" as a trigger for transaction-based workflows (as we currently have for Contact-based workflows). It's currently possible to do this for contacts but not for specific transactions.   An example of what is possible today and what I would like to do:   Context: 1 contact 2 associated transactions ("Transaction 1" and "Transaction 2")   Today:   Transaction 1 reaches phase 3 of its pipeline. A task ("ToDo A") is automatically created. This task is linked to Transaction 1 and the contact.    Another transaction-based workflow does: if "Todo A" is completed, then define "Property X" to "Yes". That will modify Property X on both Transaction 1 and Transaction 2, even if Todo A is only linked to Transaction 1 because there is no way to identify the transaction.   Tomorrow:   Transaction 1 reaches phase 3 of its pipeline and a task ("ToDo A") is automatically created. This task is thus linked to Transaction 1 and the contact.    Another transaction-based workflow does: if Todo A is completed, then define Property X to "Yes" only for transactions associated with this Todo or only for transactions in phase 3 or only for transactions with property Y value = "Yes".   I hope it's clear, and that we'll soon have a solution to this major problem that requires minimal improvement in the way workflow works (I guess) ...read more

It will be great to add as many tasks types as possible, not only Call, Email or To-Do ...read more

We have noticed that overdue tasks will default to being first in line on a timeline in a company view, however uncompleted tasks don't seem to take precedence over tasks that have already been completed (i.e. they remain in the same order that they were created in rather than having the uncompleted tasks appear just below the overdue tasks). I think if overdue tasks are able to have a visible priority over completed/uncompleted tasks, uncompleted tasks should definitely have a priority over completed tasks. [overdue] [overdue] [overdue] [uncompleted] [uncompleted] [uncompleted] [completed] [completed] [completed] ...read more

Hello hub,   My idea is that the "tasks" can have their status changed to completed according to the movement of the "deal" through the pipelines. When a "deal" passes through a step, it generates a task, so that someone can perform a certain action (call or contact, for example). In some cases, the "deal" ends up advancing to the next stage of the pipeline without the task needing to be executed, meaning that my team always needs to check the status of the deal before knowing what action to take. With the possibility of automating the "task" I could identify that my "deal" advanced in the pipeline stage and preventing my employees from needing to contact that "deal" unnecessarily. This would save my company good hours of service. * when I say deal I mean my customers who decided to continue with my purchase process. Something like a deal for a customer. ...read more

It would be great if the creator and assignor of a Task are allowed to edit/update that Task, even though they just have the permission to edit 'Owned only' Tasks. For example:  I have provided edit 'Owned-only' access for the Task object to the Sales team. When a Sales rep creates a task for the Quotations queue, they want to be able to edit the task priority based on the urgency of the request. But because they have edit 'Owned only' access, they are not able to edit the task they created and assigned. ...read more