The home page suggests a plan to end dependency on the project module, but I am not seeing that in the issues queue, only end of dependency on project releases.
I think this module should be reconstrued simply as a way to change a node's properties while adding comments. That would make it useful in a bunch of scenarios in addition to project management.
One example is I do wish to use this for project management, but my project needs are different than what the Project+ module solves. So I'd like to still use this module's features but in a different setting.
I can also see different, more generic "issue queue" type settings where a generic version of this module would be great.
Comments
Comment #1
aren cambre commentedPossible way to achieve this: #641480: Expose diff functionality to views.
Comment #2
dww@Aren Cambre: This is a long-term goal -- something we're moving towards, not something to accomplish in a single issue.
However, if all you want is to alter stuff about a node via comments, see here:
http://drupal.org/project/comment_cck
http://drupal.org/project/comment_alter_taxonomy
Comment #3
aren cambre commentedThank you. I am a little confused--why should this module exist if those two already provide the necessary tools?
Comment #4
dwwWe're making this more generic as part of #963426: [meta] Port Project issue tracking to Drupal 7 although the direction we're heading is against using comments to update the issue node. See the other issue for more info.
This module pre-dates "the necessary tools" and does a hell of a lot more than just letting you update the issue node via comments. ;) That's why it exists...
For yet another more generic solution to what you're asking about, see comment_driven. See also the Differ module (although that's currently living in a sandbox).