Ticket #1673 (closed enhancement: duplicate)
Opened 7 years ago
Last modified 2 years ago
History for milestone description text
| Reported by: | jornhansen@… | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | roadmap | Version: | 0.8.2 |
| Severity: | normal | Keywords: | tracobject version history |
| Cc: | jornhansen@…, christiansen.t@…, daved@… | ||
| Release Notes: | |||
| API Changes: | |||
Description
It would be nice to have history on the description text for a milestone like what's currently available on wiki pages.
The usage scenario for this is that sometimes you suspect a milestone description has changed since you last looked at it and you start wondering "what was changed - and when?"
Possible extensions:
- add change information like in wiki pages (user and comment) - this would answer "who changed what when and why".
- add changes to the timeline also like it works for wiki pages
Attachments
Change History
comment:1 Changed 7 years ago by cboos
- Milestone 0.9 deleted
- Owner changed from cmlenz to anonymous
- Severity changed from normal to enhancement
- Status changed from new to assigned
comment:2 Changed 7 years ago by cboos
- Owner changed from anonymous to cboos
- Status changed from assigned to new
(forgot to login)
comment:3 Changed 6 years ago by cboos
- Keywords object added
comment:4 Changed 6 years ago by cmlenz
- Summary changed from History for roadmap description text to History for milestone description text
#2521 has been marked as duplicate of this ticket.
comment:5 Changed 6 years ago by cboos
- Keywords tracobject added; object removed
comment:6 Changed 6 years ago by anonymous
- Cc daved@… added
comment:7 Changed 5 years ago by cboos
- Keywords version history added
- Milestone set to 1.0
Related to #2945.
As opposed to ticket descriptions, there's currently no workaround for getting the previous versions of the milestone description.
A change in the datamodel, as outlined in TracDev/Proposals/DataModel is in order for this one.
comment:8 Changed 5 years ago by trac@…
See also #3776.
comment:9 follow-up: ↓ 10 Changed 2 years ago by anonymous
It seems like, now that #454 is complete, one could essentially apply the same changes that were made to generate a comment history in order to generate a milestone history. If that is the case, I will probably give it a shot.
comment:10 in reply to: ↑ 9 Changed 2 years ago by cboos
- Milestone 1.0 deleted
- Resolution set to duplicate
- Status changed from new to closed
Replying to anonymous:
It seems like, now that #454 is complete, one could essentially apply the same changes that were made to generate a comment history in order to generate a milestone history. If that is the case, I will probably give it a shot.
Well, no, this has nothing to do with #454, the changes that were made for saving the comment change history for tickets can't be transposed in this situation.
Like explained in comment:7, we don't even store yet the previous versions of a milestone description, so we need some kind of drastic data model change for that, and if we do this, then it can at the same time be the occasion to find a better data model, which could accommodate the wiki, ticket and other resources and precisely remove the need for hacks of the kind of #454...
Closing as duplicate of #3776.
See TracObjectModelProposal.