View Issue Details

IDProjectCategoryView StatusLast Update
0009357mantisbtchange logpublic2013-01-25 17:10
ReporterJocelyn Assigned Todregad  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionno change required 
Product Version1.2.0a1 
Summary0009357: Change Log still shows duplicate entries
Description

This bug was marked as fixed in version 1.1.2 ( see 0008886 ), yet it still happens (see screenshot)
Or is this the intended behavior?

TagsNo tags attached.
Attached Files
mantis_bug.png (14,930 bytes)   
mantis_bug.png (14,930 bytes)   
multiple_entries.png (252,433 bytes)   
multiple_entries.png (252,433 bytes)   

Relationships

related to 0009358 confirmed Roadmap shows duplicate entries 
has duplicate 0012436 closedatrol Issue Clones with same Issue # in roadmap 
child of 0009488 confirmed Improve and fix roadmap/changelog listings 

Activities

Jocelyn

Jocelyn

2008-07-07 14:51

reporter   ~0018331

I forgot: the screenshot above is part of the page http://www.mantisbt.org/bugs/changelog_page.php
It shows some of the issues that were fixed in mantis 1.2.0

gprime

gprime

2010-05-07 03:25

reporter   ~0025434

Same problem on a 1.2.1 version (see multiple_entries.png file), multiple entries in the change log page.

One thing that is important is that the bug that is displayed multiple times is dependant of the others that are displayed multiple times to the other bugs of the same category (with "bloque" in french).

So in my case :
3077 is dependant of the 2372 (the two bugs are in the same category)
2369 is dependant of the 2372 (the two bugs are in the same category)
2310 is dependant of the 2372 (the two bugs are in the same category)
2212 is dependant of the 2372 (the two bugs are in the same category)
2032 is dependant of the 2372 (the two bugs are in the same category)
1806 is dependant of the 2372 (the two bugs are in the same category)

In changelog page, I have in the order :
3077
2372
2369
2372
2310
2372
2212
2372
2032
2372
1806
2372

Hope that helps for debugging

dregad

dregad

2012-10-16 08:59

developer   ~0033220

This is probably fixed in recent 1.2.12dev following fix of 0014718 (get a nightly build to test) - If not, feel free to reopen with additional information