View Issue Details

IDProjectCategoryView StatusLast Update
0006903mantisbtchange logpublic2008-07-24 16:51
ReporterRhasta Assigned Togiallu  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionduplicate 
Product Version1.0.1 
Summary0006903: Break up changelog page
Description

If possible it might be nice to breakup the changelog page so that when you first go to it there is just a list that links to the changelog of each individual project or the ability to view 'all'. The changelog page for an individual project could be further broken down to list the changelog for a specific version or for all versions of that project.

Just something I thought of when looking at the changelog for mantis itself, the page takes sometime to load and scrolling is difficult as more content gets loaded to the end. This functionality could already be available somewhere within mantis and I have missed it but I'm not sure.

Thoughts, comments?

TagsNo tags attached.
Attached Files

Relationships

duplicate of 0008334 acknowledged Paginate/Limit Changelog 

Activities

vboctor

vboctor

2006-04-02 00:45

manager   ~0012456

Ideally we should optimise the performance of the changelog page. I remember that someone submitted a patch at one point in time that did that.

I also agree with the recommendation here. I think the changelog page should show the following based on GET parameters on the URL:

  • All versions (like the current behaviour)
  • Index of all versions, clickable to view a specific version.
  • A specific version (only showing the issues belonging to a specific version).

The default (i.e. no parameters) should show the change log for the active project showing an index of all the versions.

Rhasta

Rhasta

2006-05-02 01:01

reporter   ~0012764

The attached archive contains both a patch file (to patch a clean 1.0.2 install) and the modified files in full. I believe it provides the desired functionality although it could probably be cleaner.

I thought I'd post it up anyway and see if it is what was intended. If it is then we can look at optimization (both of my changes by merging the foreach loops that run over all the versions and of the original changelog code itself).

vboctor

vboctor

2006-05-02 09:09

manager   ~0012765

I've attached changelog_page_vb20060502.zip which includes a single file (changelog_page.php). I've temporarily included the constant definition and the new lang entry in there to simplify the testing of the patch. This is merged with Mantis CVS code (i.e. Mantis 1.1 work in progress). I recommend that people test it and provide feedback. It is recommended to backup original changelog_page.php before installing this file.

I didn't review the code yet, and I didn't review the usability since I placed it in an installation that didn't contain any data. I may provide it on another installation later and provide feedback.

mkornatzki

mkornatzki

2006-05-07 16:21

reporter   ~0012787

thank you for this usefull patch.

i had to comment out row 191 because in mantis version 1.0.2 there is no function "bug_cache_database_result"

#bug_cache_database_result( $t_row );

Rhasta

Rhasta

2006-05-07 19:06

reporter   ~0012788

That wasn't in my original patch but I would say it's meant to be:

bug_add_to_cache( $t_row )

vbocter can probably confirm.

vboctor

vboctor

2006-05-08 05:41

manager   ~0012790

bug_add_to_cache( $t_row ) applies only if you are integrating with CVS code for Mantis 1.1 release. For Mantis 1.0.x, it should be commented out.

giallu

giallu

2008-04-22 04:30

reporter   ~0017649

This seems to be covered by 0008334.

Please comment there and, if you happen to have the patch around, feel free to reattach it.