Openbravo Issue Tracking System - Mantis @ OB
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000431Mantis @ OBOtherspublic2008-05-26 12:212008-06-24 18:22
Reporterpjuvara 
Assigned Tojaimetorre 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS20OS VersionUbuntu 7.10
Merge Request Status
Review Assigned To
OBNetwork customer
Summary0000431: Duplicate Management
DescriptionWhen a issue is rejected as duplicate, the user is prompted for a Duplicate ID, where to store the ID of the duplicate request.

That ID is stored on a header level attribute (custom attribute?) and once set is only visible in the audit section.
That makes it:
1) Not very visible (it is at the bottom of the screen)
2) Not navigable (you cannot click on the ID and open the duplicate)

It would be better if that ID would be stored also as an issue relationship of type Duplicate Of.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
has duplicate feature request 0000493 closed jaimetorre Close when duplicate loose duplicated bug ID information 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-05-26 12:21pjuvaraNew Issue
2008-05-30 18:08jaimetorreAssigned To => jaimetorre
2008-06-09 13:32jaimetorreRelationship addedhas duplicate 0000493
2008-06-24 18:22jaimetorreStatusnew => scheduled
2008-06-24 18:22jaimetorreStatusscheduled => resolved
2008-06-24 18:22jaimetorreResolutionopen => fixed
2008-06-24 18:22jaimetorreNote Added: 0007997
2008-06-24 18:22jaimetorreStatusresolved => closed

Notes
(0007997)
jaimetorre   
2008-06-24 18:22   
Now the duplicate is stored as a new relationship.