Closed Bug 732668 Opened 12 years ago Closed 5 years ago

Article history should document changes of every kind

Categories

(support.mozilla.org :: Knowledge Base Software, task, P2)

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: cilias, Unassigned)

References

Details

Right now, if I make a change to an article's slug, category, "Relevant to", topics, keywords, or mark it as obsolete, those changes are not documented anywhere. They should be documented in the article history.
Target Milestone: --- → 2012Q2
Moving 2012Q2 bugs to Future.
Target Milestone: 2012Q2 → Future
Adding Joni to the CC list.  

I really think this bug should be fixed.
Thanks for adding email notifications to this bug. However, frankly my intention was to have Sumo send email notifications on title changes only, also because that used to work in the old tikiwiki days where it sent "Wiki page renamed" emails containing "Old name:" and "New name:" lines. Not sure what's easier to implement - only that feature, or all of the above?

Also, is the purpose of this bug to add an "automatically insert applied change to history" feature? If so, that might be a bigger challenge.
(In reply to Ton from comment #4)
> Thanks for adding email notifications to this bug. However, frankly my
> intention was to have Sumo send email notifications on title changes only,
> also because that used to work in the old tikiwiki days where it sent "Wiki
> page renamed" emails containing "Old name:" and "New name:" lines. Not sure
> what's easier to implement - only that feature, or all of the above? 

If only localizers need to be notified about article title changes then that's covered in Bug 692502 - Warn localizers when an en-US article has been renamed
Email notifications should be a separate bug. This bug is about documenting changes in article history.
need this so p2 to consider if/when we get dev folks
Priority: -- → P2
See Also: → 692502
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
See Also: → 1825831
You need to log in before you can comment on or make changes to this bug.