View Issue Details

IDProjectCategoryView StatusLast Update
0009903mantisbtroadmappublic2017-10-01 14:55
Reporteratrol Assigned Toatrol  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionno change required 
Product Version1.2.0a2 
Summary0009903: Marking of Roadmap and Changelog list nesting for parent/child issues not intuitive
Description

Indent of one blank for child-issues in roadmap and changelog is not very intuitive to understand (first I thought, this is a bug)

First ask yourself, whether this is a good feature, and if yes, find another way to show the dependencies

maybe another kind of marking would be more intuitive

just a quick idea:
":" instead of "-" and two blanks instead of one

  • 0009488: [roadmap] Improve and ...
    : 0008307: [roadmap] Roadmap must have .....

or something like:

  • 0009488: [roadmap] Improve and ...
    `- 0008307: [roadmap] Roadmap must have .....

or

  • 0009488: [roadmap] Improve and ...
    \ 0008307: [roadmap] Roadmap must have .....

.....

TagsNo tags attached.
Attached Files
new indent.jpg (20,888 bytes)   
new indent.jpg (20,888 bytes)   

Activities

stefang

stefang

2008-11-27 08:51

reporter   ~0020080

Last edited: 2008-11-27 09:33

Yeah, I fully support that!
Here's my suggestion "|_" and the changed code in <b>custom_function_api.php</b> of Mantis release 1.1.5:

<ol><li>In function <b>custom_function_default_changelog_print_issue</b> change line 48:

<pre>echo str_pad( '', $p_issue_level * 6, ' ' ), '- ', string_get_bug_view_link( $p_issue_id ), ': ', $t_category, string_display_line_links( $t_bug->summary );</pre>
to

<pre> switch($p_issue_level)
{
case 0:
echo str_pad( '', $p_issue_level 6, ' ' ), '- ', string_get_bug_view_link( $p_issue_id ), ': ', $t_category, string_display_line_links( $t_bug->summary );
break;
default:
echo str_pad( '', 12+($p_issue_level-1)
18, ' ' ), '|_ ', string_get_bug_view_link( $p_issue_id ), ': ', $t_category, string_display_line_links( $t_bug->summary );
break;
}</pre></li>

<li>And in function <b>custom_function_default_roadmap_print_issue</b> change line 79:

<pre>echo str_pad( '', $p_issue_level * 6, ' ' ), '- ', $t_strike_start, string_get_bug_view_link( $p_issue_id ), ': ', $t_category, string_display_line_links( $t_bug->summary );
</pre>
to

<pre> switch($p_issue_level)
{
case 0:
echo str_pad( '', $p_issue_level 6, ' ' ), '- ', $t_strike_start, string_get_bug_view_link( $p_issue_id ), ': ', $t_category, string_display_line_links( $t_bug->summary );
break;
default:
echo str_pad( '', 12+($p_issue_level-1)
18, ' ' ), '|_ ', $t_strike_start, string_get_bug_view_link( $p_issue_id ), ': ', $t_category, string_display_line_links( $t_bug->summary );
break;
}</pre></li></ol>

<b>Please note, that this is only a quick and dirty hack!</b>

milliams

milliams

2009-03-31 08:36

reporter   ~0021335

I agree that this way of displaying child relations is much better

atrol

atrol

2017-09-20 16:35

developer   ~0057769

Setting to resolved as the roadmap looks better in terms of child issues in version 2.x.