Do we for sure need a "500 task limit"?

[DougLucas]

I just hit the limit -- and received the warning sign at the top of the Task Module that I've hit the 500 task limit. Unfortunately, I'm designing a strategic plan for an entire 25-person work group. I'm not sure how to deal with it. Do we for sure need such a limit? Is it performance driven? Could we give this power to the user or administrator (to choose the upper ceiling?)

Doug

[DougLucas]

And if we *do* need this 500-task limit, could we create a task counter indicator somewhere on the Task Module screen, so the user has some warning when he/she is approaching this limitation?

I note that creating a sub-workspace (a "child") doesn't work. Feng still considers tasks within sub-workspaces as part of the 500-task limit. I had to create a workspace completely apart, branching off part of my hierarchy to that workspace.

Creating a filter to show only a portion of the tasks wouldn't work for me, because there will be many times I'll want to see the entire set of tasks as a whole.

Thanks to everyone for their work on Feng Office.

[fernandog]

I had the same problem, but I found the code where the limit is set

In applications/controllers/TaskController.class
(open with > wordpad)
Change the line:
$tasks = ProjectTasks::findAll(array('conditions' => $conditions, 'order' => 'created_on DESC', 'limit' => '501'));

The number "501" i changed it to "1001" and now I can see 1000 tasks.

Im not a programmer but I havent experienced any other consequences to this change,

[koko]

Hi,

Thanks for solving this issue ...
I think the set there for performance reason, no? On many hosts, you only have 30 seconds to run a PHP-script and getting 1000 tasks from somewhere can take longer. Especially when you're on shared hosting.

[DougLucas]

Thanks Fernandog. We'll try bumping up the limit too and will report back here how our performance is affected, if at all. Thanks again.

[fernandog]

Ahh, also forgot to add

In the same file, change this line
         if (count($tasks) > 500) {
            tpl_assign('displayTooManyTasks', true);
         }

Change the number "500" to "1000" (or whatever limit you've set) to get rid of the warning.

[DougLucas]

Did anyone else notice that this limit is adjustable by the user ("Account") under tasks? We're setting all ours to 1000 with little, if any, perceived performance hit.

[fernandog]

Yes this was just added in version 1.6.2 according to the release notes perhaps because of this very discussion

[scept1c]

can I remove the limit completely by putting a greater number?

[cabeza]

Yes this was just added in version 1.6.2 according to the release notes perhaps because of this very discussion

It was designed this way for performance only ...
... and scheduled for dev because of this thread.