Actions
Feature #2503
closed
History of Ticket-Description
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2009-01-13
Due date:
% Done:
0%
Estimated time:
Resolution:
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 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by
Actions