misc features > Feature

option in person-profil if tasks can be approved / #482

MoveBookmark

Summary

v0.3- timing tasks
open
Mar 22, 2006
2 hours ... 4 hours
Mar 22, 2006 / pixtur
Jun 9, 2007 / xl
View previous 8 versions
 

Attached files

No files uploaded
  • we should distinguish the behaviour of people in projects, depending on project-role:
    • normal users can change state to "completed?"
    • project-managers and admins can change to anything
  • Not sure how to handle "delete"-function, though

related:

7 Comments

burger

Sep 5, 2006
View comment
Hello Tom,

so only admins and project manager should be able to choose "new", "open", "blocked", etc.?
Developer, tester etc. should only have the option "completed?"?

Do I understand it right?

pixtur

Sep 7, 2006
version 2
Not sure...
You are a PM... What do you think? Is this a good behavior or does it just keep people from doing their jobs? Since streber wants to be a friendly wiki application restricting users might not be nice. Maybe there are other ways to prevent from vandaslism, like searching for "tasks not approved by PM".

binder

Sep 7, 2006
version 2
Reply to Not sure...
I think it's a simple matter of hierarchy (sad but true *G*):
  1. the only one to delete an item (task, project, person,...) is a PM/admin
  2. a developer/designer should only be able to set the status "completed?"
    • the PM then can "approve" the completed? item
    • the PM also can re"open"
That's the only way for the PM to stay up to date, if he has to keep in touch with different projects and much more different tasks...

pixtur

Sep 8, 2006
hmm.
So this sounds like just another project option. Or should it be an option for the team member?



binder

Sep 8, 2006
Reply to hmm.
it could be a team-member option, but I don't think that's neccessary...
keeping it simple and stupid, it should be a global project-option.

pixtur

Sep 8, 2006
Just had my lunch...
Now I am sure, that it should be an option for each team member. Those options should be part of the user's profile, and then be copied to the project team membership.
It will not be more work but a little bit more flexible.



xl

Jun 9, 2007
hmmmm
in our case, if we want to restrict, then it should be a project option "persons able to approve".
but i would soggest another path: no restrictions.

what if me as a pm has the option to define a filter (or have a pre-defined) "evil actions. including approval ba non-pms.
in my "changes" mail those actions would be marked specially.

wouldnt that be wiki spirit, but also enforcing hierarchy?
 
 

Comment / Update