View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011721 | mantisbt | preferences | public | 2010-03-29 08:52 | 2018-05-23 07:15 |
Reporter | Hein_Meijer | Assigned To | |||
Priority | normal | Severity | tweak | Reproducibility | always |
Status | new | Resolution | reopened | ||
Summary | 0011721: preferred setting at what moment the bug number becomes strikethrough | ||||
Description | When a bug is reported "resolved" the bug number (text) becomes strikethrough (strikeout) | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
You can set Be aware that this affects also other functionality |
|
The suggestion was to create a setting to define at what status a bug number gets displayed with a strike-through. Something like: $g_bug_receive_strikethrough_status = RESOLVED; Plus adding the possibility to not use strikethrough at all. Thank you for your suggestion, but unfortunately i don't think that's a useful alternative because like you say it affects (too much) other functionality. |
|
First I thought about reopening this issue as a new feature request. For example have a closer look at function custom_function_override_roadmap_print_issue |
|
Hello atrol, 1. I just noticed the configuration option was suggested (but not implemented) by vboctor here: 0007808:0014157 2. This was not done to be "consistent" by the way, because in the View_all_bug page bugs with a status >= $g_bug_resolved_status_threshold are NOT striked-through either. So, my preference would be: do not strike-through bug numbers in the changelog page. |
|
What about just changing a.resolved in default.css to { text-decoration: underline; } ? Result: TBH, I don't know why there is a difference of implementation in "Change Log" and "Roadmap" . This was before the time I started with MantisBT I think this will all be changed when 0004227 and 0006628 will be realized. |
|
That result sounds OK to me. It would fix item 2 mentioned in my previous comment. To fix item 1, a new configuration option ($g_bug_strike_status_threshold) would have to be added. However this is just my point of view, its probably a good idea to ask opinions of some others :) |
|
Did you try changing the css ? |
|
Yes I have tested it, the result is: strike-through is no longer used anywhere (changelog, roadmap, bugnotes, bug descriptions, etc.) It does not solve item 1 because we only want for example issues with a status of "closed" (not "resolved") to be striked-through, which could be accomplished by using a configuration setting ($g_bug_strike_status_threshold). |
|
Seems that we are talking about differnt things You wrote
I thought this was your item 1, and your problem was that you are not able to change the behaviour for descriptions and bugnotes The feature request of Hein_Meijer is not solved. |
|
Hi Atrol, well what Hein_Meijer wants is: This would be solved by Item1: adding a configuration setting $g_bug_strike_status_threshold. $g_bug_strike_status_threshold = "CLOSED" would achieve this because the result would be striking through bugs with status "CLOSED", instead of what Mantis currently does: striking through bugs with status "RESOLVED". |
|