View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008334||mantisbt||change log||public||2007-09-05 09:05||2019-06-22 07:32|
|Summary||0008334: Paginate/Limit Changelog|
Changelog can grow until it's a very large (and slow rendering/loading) page. Have it paginated or limited (versions could have a new check to include or not in changelog) would be a nice option.
|Tags||No tags attached.|
I agree about the need for limiting the versions to be included. I can see several approaches for this:
I would like feedback about preferences for these options or other possible solutions.
I would prefer a paged solution and not a limitation. What do you think about a "Limit the number of ISSUES per page" to dertermine the page-break ?
But now to your other options:
To 1. & 3.: Sometimes we have versions with a very small amount of fixed issues. Maybe in a range within ten. So a visualization using the settings 1 and 3 would be very very short. And not very useful to us.
To 2.: This seems a good solution in general, but for the requirements of our ISO-9000 certification we need to see all changes so this option would always be "ON" for us here. Another thought for your schema change. Have you ever thought of using the severaly bits of an integer "State" value instead of generating a boolean option for each and everything? This could prevent schema changes when you need another "On" or "Off" option in the future. It's a bit of readability against a database change mess.
Best choice for me could be to have a issue amount limited page, but including/excluding entire version changelogs, and possibility to see next/previous pages.
I totally agree to your example Bithunter! Including the whole version is a very good idea.
Jira is implementing 1. with default to last 3 versions.
Now that we have an Obsolete field, I think we can show a changelog page with the last 3 released, not obsolete versions.
Two links could provide the changelog for
the magic number "3" could be replaced by a configuration option, global or per-user
|2007-09-05 09:05||Bithunter||New Issue|
|2007-09-05 21:00||vboctor||Note Added: 0015573|
|2007-09-05 21:00||vboctor||Status||new => acknowledged|
|2007-09-06 02:58||Ellerbrok||Note Added: 0015576|
|2007-09-06 10:56||Bithunter||Note Added: 0015580|
|2007-09-07 04:21||Ellerbrok||Note Added: 0015587|
|2008-04-21 18:56||giallu||Note Added: 0017647|
|2008-04-22 04:30||giallu||Relationship added||has duplicate 0006903|
|2008-04-22 04:50||giallu||Relationship added||has duplicate 0006017|
|2019-06-22 07:32||atrol||Relationship added||related to 0017145|