Opened 20 years ago
Closed 20 years ago
#1352 closed defect (fixed)
Terminology: ticket changelog
Reported by: | anonymous | Owned by: | Christopher Lenz |
---|---|---|---|
Priority: | low | Milestone: | 0.9 |
Component: | ticket system | Version: | 0.8.1 |
Severity: | trivial | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Changelogs start w/ the oldest entry first. This always makes it necessary to scroll down to see the last (newest) entry. I'd prefer to have this the other way round (starting w/ the last entry).
This would IMHO also complement #1326, since it helps to see important details of a ticket as fast as possible.
Attachments (0)
Change History (7)
comment:1 by , 20 years ago
Component: | general → ticket system |
---|---|
Milestone: | → 0.9 |
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 20 years ago
I don't see why "Changelog" suggests a particular ordering. I think the word is just fine: it's a log of the changes. I'd rather keep the label short. "Modification History" is unnecessarily verbose.
comment:3 by , 20 years ago
While the word Changelog in itself doesn't suggest any order, there's a common practice of recording changes with the most recent changes first in Changelog files. That's why I think there's a connotation.
Would History be better? It's shorter, and it suggests the chronological order…
Mantis for example uses Bug history, JIRA uses Change History …
comment:4 by , 20 years ago
I have no problem with the current terminology, but Change History would also work for me.
comment:5 by , 20 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
Summary: | Order of changelog entries → Terminology: ticket changelog |
comment:6 by , 20 years ago
Priority: | normal → low |
---|---|
Severity: | normal → trivial |
Status: | new → assigned |
comment:7 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Changed to "Change History" in [1700].
Most of the time a comment is responding to previous comments, so I don't think it would make sense to read them in reverse order.
But you have a point in that the Changelog term used for the title suggest the other way round (most recent first).
I'd suggest renaming Changelog to Modification History.