View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009903 | mantisbt | roadmap | public | 2008-11-26 16:29 | 2017-10-01 14:55 |
Reporter | atrol | Assigned To | atrol | ||
Priority | normal | Severity | tweak | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 1.2.0a2 | ||||
Summary | 0009903: 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:
or something like:
or
..... | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Yeah, I fully support that! <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> <pre> switch($p_issue_level) <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> switch($p_issue_level) <b>Please note, that this is only a quick and dirty hack!</b> |
|
I agree that this way of displaying child relations is much better |
|
Setting to resolved as the roadmap looks better in terms of child issues in version 2.x. |
|