Hello,

  • First of all, a great, great module. I have created PM sites using a whole slew of CCK types and yours is very economical and beautifully done.
  • Second, the ability to assign accountability of a task to an individual associated with a project (Could be a simple drop down of persons with : task leader assignment as the field title)
  • Third, a simple "Approval" functionality: Designate a page or content with "Needs approval" and a drop down of people (again associated with the project) ... the people who are designated, could see a "needs approval" indicator when they view the list of tasks, when they view the items, they could select (yes, no, or anyother of the way, way cool attributes that you allow the uses to set up)

Just a thought.

Also, if you would like to brainstorm on functionality, I would love to show you my own versions of "Base Camp" that incorporates Views and Panels to create a landing page of associated content.

All just suggestions as it is an excellent module!

Cheers

Comments

Roberto Gerola’s picture

Roberto Gerola commented

>First of all, a great, great module. I have created PM sites using a whole slew of CCK types and yours is very economical and beautifully done.
Many thanks

> Second, the ability to assign accountability of a task to an individual associated with a project (Could be a simple drop down of persons with : task leader assignment as the field title)
Yes, I am yet thinking how to implement this. I think that many persons could be assigned to a single task, but only one can be accountable for it.
This would have a large impact on permissions at this point, so I need to devise a better integration with Drupal access apis.

>Designate a page or content with "Needs approval" and a drop down of people
Could you explain it a a bit more ?
Tasks would need approval before they start ?

Thanks, Roberto.

johnvsc’s picture

johnvsc commented

Hi Roberto :)

On the approval: many times, when I am working on a project (I am primarily a designer) I need to post something so that some one in the chain of command and say yea or nay. Now, I have by-passed this procedure by asking everyone to give a comment on it... and that works out fine for the most part... except i have to read all of the comments and, well, that can get hairy some times

however, most times, several people need to "sign off" on a proof before it can go to a printer or be posted online. in the non digital world, they would in initial the proof and send it back (if any thing went wrong, you can say, "um, but you approved it") ... i would like the same accountability in a digital realm

ok, the great thing about using STORM is that it is an effective communication tool: so, if there were several people that needed to "sign off" on a "task" (i am using task because that is the most appropriate, i think) ... it would be good to have a "is approved by" list.

The majority of the usage would be one person signing off ... but i thought that extending it to project users would be beneficial too (if you can do it for one, you can do it for many)

The "5 Star" rating module gave me the idea...

does this help?

oh, another thing: is there a way to use views to serve up only the projects that a person has permission to ? or, on second thought, this would be handled by content_access (waiting, feverishly for a 6.0 version)

thanks

Magnity’s picture

Magnity commented
Status: Active » Closed (won't fix)

2: dealt with by #392414: Assign projects, tasks, and tickets to people
3: I think the best way to do a 'signoff' or similar would be to use notes attached to the task. If you wish, you can also have cck fields on the note - perhaps such as "signoff", "needs work" etc. -> therefore a won't fix on this bit.