@chad I am sorry, can you mention these ways around in detail. I am not sure if I caught one. Don't you think blocking tasks should inherently block the parent tasks else what is the difference between blocking tasks and subtasks?

It's ok if they do that. The system needs to be right. If users find ways to cheat the system that is fine by me :-)

Thanks! That did it.

Thanks avivey. Let me explain what I want to do, then perhaps you could help me in the best way possible.

I am missing something in this step: "Adding these commands to sudoers will allow the daemon and webserver users to write to repositories as the daemon user."

Okay so I found where this setting was and have set a password now but I still get the same Initialization Error.

I think there could be more use for them than that. Is there a way I can monitor performance of my team?

Got it, thanks a lot.

In T7605#102403, @sshannin wrote:

The way my install handles this is by composing task creation URL's which set a lot of the fields. Then we throw this onto a panel in the default dashboard.

So we have a link like "File Product Bug" which opens up a ticket template, prepopulates CC's, projects, and even a message template. We don't do any visibility settings, so I'm not sure if those can be set via get params, but if they are this might be an easy way for you to go.

sshannin, thanks for your reply. I guess that can work. But is there a more scalable way to do this?