Greetings!

When you change something to the fields in an issue, you get a history in the comment, showing what changed.
Example: issue: fixed -> closed

Is there a way to do that "manually" with regular cck fields? maybe using comment cck?
My site has public fields using comment cck, where changes should be tracked openly.
I have no clue how to add this to the comment tpls manually, because me do not know how to retrieve the overwritten value (nor how to store it in a comment).

Any help is very much appreciated!

Thanks!

Comments

aclight’s picture

aclight commented
Assigned: Unassigned » aclight
Status: Active » Fixed

As far as I know the comment_cck module allows you to change the value of CCK fields from a comment on a node, but it doesn't keep a record of where such changes were made, so displaying information about changes made in a comment wouldn't be possible.

Keeping track of the value of fields (whether CCK or fields that project_issue uses internally) is not a trivial thing to do. If you are considering writing a module for your site that does so, you might check out the Comment alter taxonomy module, which does this for taxonomy terms and lets users change the terms from comments. Note, however, that you'll still need the project_issue module (or other code you write yourself) if you want to display changes made to the terms assigned to an issue.

There have been suggestions that we move the functionality in the project_issue module that handles display of these metadata tables into a new module so that people could, for example, use the comment_alter_taxonomy module on their sites to track and display changes to terms on a node made from comments without installing the project_issue module.

But as far as I know there is currently no easy solution to do what you want to do, at least outside of the project_issue module, which does not currently support tracking changes to CCK fields.

farald’s picture

farald commented

Oh silly me!
With a bit of comment testing, I realized that comment_cck actually DOES do exacly the same as I suggested here.

It creates a history for every cck field changed and write them to the comment.
EXACLY the way the issue tracking system does it!

So, so much talk for nothing, but I already have the features I wanted, so Im happy! :D

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.