Flyspray

  • Status Closed
  • Percent Complete
    100%
  • Task Type Feature Request
  • Category Backend/Core
  • Assigned To
    Dexpot
  • Operating System All
  • Severity Low
  • Priority High
  • Reported Version 0.9.3.1
  • Due in Version 0.9.6
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray
Opened by nopps - 19.08.2003
Last edited by Anonymous Submitter - 28.08.2004

FS#91 - History of changes would be nice to have

Sometimes the complete history of changes to tasks could be useful for reporting.

[modified slightly to test the latest patch - Tony]

Closed by  Anonymous Submitter
31.08.2004 02:16
Reason for closing:  Implemented in devel
Additional comments about closing:  

Great work, Patrick!

Anonymous Submitter commented on 22.08.2003 08:23

I assume that you mean just changes to the top area with Task Type –» Details? This sounds like a good idea. It will be done by the next release.

nopps commented on 22.08.2003 19:05

The ultimate goal would be to do a complete revisioning of all related information. Since it’s possible to change e.g. comments for any member of the admin group, this could be misused to malisciously change a report. This doesn’t need to be done intentionally. Often, after some time, one sees things differently and one recognizes that exactly the comment that has been modified or deleted by oneself to make things look better contained the clue to the problems solution. Who made that comment, what was it like before it was
log changes to the Task Details is the first step, and in my eyes the most important, into this direction. Perhaps it’s a good idea to add a textarea for a log message to the task details editing form within which one could describe briefly the changes done.


Hi,

I made a changelog script last night because I had similar requirements (to see new comments and new tasks in reverse chronological order). This looked like the best place to contribute my code back to Flyspray in the hope that it’s useful!

The script itself is within a password protected area of the site so I can’t show a demo, but the source is

Place this in the scripts directory, then visit {installation dir}/index.php?do=changelog

I hope this is
wishes & thanks for a great
Latham


in progress...

Anonymous Submitter commented on 17.05.2004 02:35

I’m not always on the notification list to every task, so the best place to contribute back to Flyspray is via the mailing list.

[Edited this comment to test latest History patch -Tony]

Anonymous Submitter commented on 22.05.2004 00:12

Applied Patrick’s first patch for this task. History enabled on this BTS.

kevin commented on 03.08.2004 21:12

Not sure if this is a PgSQL-specific thing or not, but...

At this point, the old_value and new_value fields are both limited to 100 chars - which is not enough for the Task Details or Comments fields. I - and my users - are running into this limitation.

It’s rather VARCHAR specific. Postgres schema uses TEXT fields instead of VARCHAR and doesn’t have upper length
– fetch the latest SVN copy and stop using your upgrade script ;)

Anonymous Submitter commented on 10.08.2004 10:07

Changed mysql schema fields from VARCHAR to
is there anything remaining to be done on this task?

Yep. Changing the column to TEXT won’t have any effect because the code doesn’t save the details of such ‘fulltext-changes’. That still needs to be implemented...

Logs new and previous values when editing task details, comments, ... - patch against r123

(application/octet-stream)    history2.diff (11.9 KiB)

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing