View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0029257 | mantisbt | bugtracker | public | 2021-11-09 10:39 | 2021-11-26 15:16 |
Reporter | cas | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 2.25.2 | ||||
Summary | 0029257: Duplicate-id is always shown when resolving an issue | ||||
Description | in bug_change_status.php the following code is used to determine if the duplicate-id should be shown: | ||||
Tags | No tags attached. | ||||
Remember we're generating a static page here - we need the Duplicate ID field shown so it is available when users select duplicate resolution. Otherwise, some JavaScript would be required to dynamically show/hide the field depending on value selected in Resolution. The Duplicate ID field will be hidden when resolving an issue that has a relationship of type BUG_DUPLICATE. |
|
Oops, I would have expected it to work just the other way around..... |
|
This is debatable I guess, but the rationale is that we already have an associated duplicate bug ID in this case, so there is no need to ask the user for another one to add (which is what this field does). |
|
This needs to be validated. Because when I resolve an issue with resolution "Duplicate" there is no mandatory registration of the duplicate issue id which I would have expected based upon your explanation. |
|
True, we currently do not enforce that. This allows the flexibility to mark an issue as duplicate, without requiring to specify an actual duplicate relation. If the current behavior is not satisfactory for you, then I suggest you provide a detailed specification of how you think it should work. Consider also the case of admins that may not want this to be mandatory; also what should happen in the case of multiple duplicates (technically possible since relationships are many-to-many), and in an upgrade scenario where duplicate relationship is mandatory, what to do with existing issues that do not have one. It could also happen that a duplicate relationship is deleted after the issue has been resolved; what to do in this case ? Based on the above, I'm personally not in favor of making duplicate id field mandatory but again I'm open to discussion. |
|
I have to agree, given your arguments, that we should not make it mandatory. The field does not bother me personally, I looked into this because of a forum question |
|