Recent posts in this topic
After working with tickets for a day: briefly, what we want is a container (task list, tickets, whatever you want to call it) with subtasks that CAN THEMSELVES BE COMMENTED ON. A 'task' can quickly balloon into many subtasks, and many of these can lead to involved, linked discussions. This is VERY hard to track in the current format.
In fact, as I am moving tasklists to tickets, it is quite frustrating that I cannot comment on the tasklists or embedded tasks, simply to say "moved to X location" instead of "completed."
As an admin, I should have control to set author of items (OK, I can hack the SQL ...)
More later.
In fact, as I am moving tasklists to tickets, it is quite frustrating that I cannot comment on the tasklists or embedded tasks, simply to say "moved to X location" instead of "completed."
As an admin, I should have control to set author of items (OK, I can hack the SQL ...)
More later.
patricio.keilty
on Oct 22. 2007. 5:41 am
rainhard:I'm having a problem with permissions when using the "Task Commenting Hack":
I have 3 users assigned to one project. User1 assigns a task to User2, User2 adds a comment to this task. The problem is, that User3, who wants to have a look what is going on in this task, doesn't have the permission to access "task details". This is a problem because User3, who is also familiar with this project could add some valuable input, even if the task is not assigned to him.
How and what could I change in the configuration so that every user assigned to a specific project can access and comment all tasks in this project?
Hi,
i´m experiencing same problem as rainhard, client users are not able to add comments on tasks assigned to any of the members, getting a "You don't have permissions to access requested page" error message. For tasks assigned to "Anyone" comments are allowed instead.
Any update on this?
Thanks in advance,
--p
