Feature #746

Versioned issue descriptions

Added by Ben Oakes over 9 years ago. Updated over 6 years ago.

Status:ClosedStart date:2008-02-27
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:1.2.0
Resolution:Fixed

Description

It would be very useful to be able to have the ability to track changes to a description over time, much like a wiki. Currently, to get around this limitation, we have been tracking changes by adding notes. This is important because we may want to update a description to more closely match our understanding of a problem, but we would still like to keep what a bug reporter or feature requester originally said in case there is a mixup.


Related issues

Related to Redmine - Patch #1717: Show diff for issue description change Closed 2008-07-30
Duplicated by Redmine - Feature #328: Log any changes to the issue. description ,subject etc. Closed
Duplicated by Redmine - Feature #2503: History of Ticket-Description Closed 2009-01-13
Duplicated by Redmine - Feature #4811: Track changes to issue descriptions like wiki content Closed 2010-02-11

Associated revisions

Revision 4954
Added by Jean-Philippe Lang over 6 years ago

Keep track of issue description changes (#746).

History

#1 Updated by Ronie Henrich over 9 years ago

+1

#2 Updated by Artem Vasiliev over 9 years ago

+1
To me it's very major feature, implemented brilliantly in Trac not a long ago.

#3 Updated by Artem Vasiliev over 9 years ago

Description change even doesn't go to change history, but that's another story (with an easy hack-around): #328

#4 Updated by Artem Vasiliev about 9 years ago

Patch created closing this issue, #1717

#5 Updated by Reach Everywhere over 8 years ago

+1

#6 Updated by Ben Oakes over 7 years ago

@Artem: should this issue be closed? (Has the patch been accepted?)

#7 Updated by Felix Schäfer over 7 years ago

  • Status changed from New to Closed

Closing this issue in favor of #746.

#8 Updated by Felix Schäfer over 7 years ago

  • Category set to Issues
  • Status changed from Closed to Reopened

Sorry, I had entered the relation the wrong way round.

#9 Updated by Randy Syring about 7 years ago

fwiw, +1 :D

#10 Updated by Marek Siller almost 7 years ago

+1 it would be a nice feature to have.

#11 Updated by Aleksander Palyan almost 7 years ago

I wrote new plugin for this feature.

You can try to use this plugin: https://github.com/freedayko/redmine_issue_history

#12 Updated by Mischa The Evil almost 7 years ago

Aleksander Palyan wrote:

I wrote new plugin for this feature.

You can try to use this plugin: https://github.com/freedayko/redmine_issue_history

I've did some quick testing and it seems like you've integrated the functionality of the patches provided for issue #1717 smoothly and nicely.

Thanks for your contribution.

#13 Updated by Mischa The Evil almost 7 years ago

Mischa The Evil wrote:

Aleksander Palyan wrote:

I wrote new plugin for this feature.

You can try to use this plugin: https://github.com/freedayko/redmine_issue_history

I've did some quick testing and it seems like you've integrated the functionality of the patches provided for issue #1717 smoothly and nicely.

Just to let you know: I think I found an issue and filed it at https://github.com/freedayko/redmine_issue_history/issues/.#issue/1 -> Issue has been fixed by plugin author.

#14 Updated by Leonard Brünings almost 7 years ago

I think this should be part of the Redmine core, but for now we will try the plugin.

#15 Updated by Jean-Philippe Lang over 6 years ago

  • Subject changed from Versioned Descriptions to Versioned issue descriptions
  • Status changed from Reopened to Closed
  • Target version set to 1.2.0
  • Resolution set to Fixed

Feature added in r4954. Description changes are now saved and diffs can be viewed from the issue history.

The implementation makes use of the existing issue history models which makes it radically different from the proposed plugin.

#16 Updated by Dominic Clifton over 6 years ago

  • Status changed from Closed to Reopened

Is the plugin by Aleksander Palyan compatible with the upcoming 1.2.x release? If not is there a simple way to migrate from the plugin when 1.2.x is released?

Thanks everyone for your work on this, it's a very handy feature!

#17 Updated by Etienne Massip over 6 years ago

  • Status changed from Reopened to Closed

Please ask the plugin author.

#18 Updated by Ben Oakes over 6 years ago

Great to see. Thanks for taking the time to implement this, Jean-Philippe Lang.

Also available in: Atom PDF