Tasks not listing under project - for a reason or time for a bug report?

I hope this is the right place to discuss,
I’m running 8.9.0 and trying to figure things out (Totaly new to CRM’s in general, sysadmin/devop person).

I created a project. When i go to the ā€œMoreā€ menu, select the Task module and add a task (Selecting ā€œprojectsā€ as relation and adding the projects name) the task is not listed on the project overview page.

When i add a task to the project through the project page, it does list the task.

Maybe this is for a reason and i simply don’t know it yet because of being a CRM noob. To me it feels like a bug. Maybe i did something else wrong.

Any related comment is welcome before i post it as a bug :slight_smile:

1 Like

Check the release notes for v8.9.1 and v8.9.2, if you do not find in it; raise an issue on GitHub.


Hello,

there are Tasks and Project Tasks in the CRM.

If you’re working with Projects, try to stick to the Project Tasks.
You’ll see, that they have way more features / advantages within a project.

Tasks are independent from Projects and are meant to be used more as individual to dos - not necessarily project related.

I’ve not try to relate a task to a project with the flex relate (since relating the task to the contact / account / opp had usually a higher priority). But I’ve added a custom relationship to ā€œgroupā€ tasks around a project.
However, that was quite a custom situation.
Try to stick to the standards as far as possible and things are easier in the long run.

Do projects tasks not work for you?
If so, why?

I’ll look further into the changelogs.
Figured i’d just try an upgrade to 8.9.2 but that ended in a not working instance :slight_smile:

PHP Fatal error: Uncaught Symfony\Component\DependencyInjection\Exception\RuntimeException: Cannot autowire service ā€œApp\SystemConfig\LegacyHandler\SystemConfigHandlerā€: argument ā€œ$recordViewAttachmentLimitsā€ of method ā€œ__construct()ā€ is type-hinted ā€œarrayā€, you should configure its value explicitly. in /var/www/html/crm/vendor/symfony/dependency-injection/Compiler/DefinitionErrorExceptionPass.php:51\nStack trace:\n#0 /var/www/html/crm/vendor/symfony/dependency-injection/Compiler/Compiler.php(80): Symfony\Component\DependencyInjection\Compiler\DefinitionErrorExceptionPass->process()\n#1 /var/www/html/crm/vendor/symfony/dependency-injection/ContainerBuilder.php(767): Symfony\Component\DependencyInjection\Compiler\Compiler->compile()\n#2 /var/www/html/crm/vendor/symfony/http-kernel/Kernel.php(506): Symfony\Component\DependencyInjection\ContainerBuilder->compile()\n#3 /var/www/html/crm/core/backend/Kernel.php(113): Symfony\Component\HttpKernel\Kernel->initializeContainer()\n#4 /var/www/html/crm/vendor/autoload_runtime.php(43): App\Kernel->init()\n#5 /var/www/html/crm/public/index.php(5): require_once(ā€˜ā€¦ā€™)\n#6 {main}\n thrown in /var/www/html/crm/vendor/symfony/dependency-injection/Compiler/DefinitionErrorExceptionPass.php on line 51

Something to look into tomorrow :slight_smile: