Feature #2503
closed
History of Ticket-Description
0%
Description
It is a pitty that changes of the description of an issue are nowhere stored. So you can never be sure, the description is what is was or what it should be :-)
I built a workaround for myself, by copying the description to a shallow wiki-page, where I can see the history. Obviously more a bad hack, than a good solution. I paste the patch anyhow to illustrate what could be a solition. Using the wiki as "storage" for the history is maybe not such a bad idea after all.
Index: /usr/local/workspace/redmine/app/models/issue.rb
===================================================================
--- /usr/local/workspace/redmine/app/models/issue.rb (revision 2263)
+++ /usr/local/workspace/redmine/app/models/issue.rb (working copy)
@@ -152,7 +152,21 @@
:prop_key => c.custom_field_id,
:old_value => @custom_values_before_change[c.custom_field_id],
:value => c.value)
- }
+ }
+ # edit corresponding wiki page if of type use case
+ if self.tracker_id == 6 and @issue_before_change.description != self.description # only tracker 6. hard coded magig number, brrr :-(
+ wiki_page = self.project.wiki.find_or_new_page( subject )
+ wiki_page.content = WikiContent.new(:page => wiki_page) if wiki_page.new_record?
+ content = wiki_page.content_for_version( nil )
+ content.comments = nil
+ content.text = self.description
+ content.author = User.current
+ wiki_page.new_record? ? wiki_page.save : content.save
+ end
@current_journal.save
end
# Save the issue even if the journal is not saved (because empty)
Related issues
Updated by Mischa The Evil almost 16 years ago
See patch #1717 which holds a working patch to adress this issue. It also provides an idea of implementing it in the core.
I'll relate the issues...
Updated by Thomas Rekittke almost 16 years ago
- Status changed from New to Resolved
Updated by Robert Pollak over 15 years ago
In which Redmine release is or will this be contained?
Updated by Mischa The Evil over 15 years ago
- Status changed from Resolved to New
Wrapped the code into pre-tags and corrected the issue-status.
Updated by Martin Schneider over 15 years ago
Thomas Rekittke wrote:
It is a pitty that changes of the description of an issue are nowhere stored. So you can never be sure, the description is what is was or what it should be :-)
Independent from the implementation, this is a great feature! Please make this feature part of the core. Additionally it would be nice if the comments would have a history too. So the "can edit comments" rule gets a new aspect.
BTW:
Thanks for Redmine! It is pretty cool!
Updated by Marek Kreft over 15 years ago
Hi,
When can we expect this feature (or its alternative) to be implemented in Redmine core?
Updated by Marek Kreft over 15 years ago
Hello again.
This is what I figured out today. I think that this small fix improves things quite well.
In place of
if self.tracker_id == 6 and @issue_before_change.description != self.description # only tracker 6. hard coded magig number, brrr :-( + wiki_page = self.project.wiki.find_or_new_page( subject ) + wiki_page.content = WikiContent.new(:page => wiki_page) if wiki_page.new_record? + content = wiki_page.content_for_version( nil ) + content.comments = nil + content.text = self.description + content.author = User.current + wiki_page.new_record? ? wiki_page.save : content.save + end
I've added this
if @issue_before_change.description != self.description
@current_journal.details << JournalDetail.new(:property => 'cf',
:prop_key => 'description',
:old_value => @issue_before_change.description,
:value => self.description)
It was tested on trunk version and works like charm.
Updated by Felix Schäfer over 14 years ago
- Status changed from New to Closed
Closing this issue in favor of #746.