- $g_relationship_graph_enable
This enables the relationship graphs feature where issues are represented by nodes and relationships as links between such nodes. Possible values are ON or OFF. Default is OFF.
- $g_graph_format
Graphviz output format. Can be
svg
,
png
(default) or any other
supported format.
svg
produces higher quality images compared to
png
, but it requires Graphviz >= 2.42.4 due to a
bug in earlier versions. The fix will be included in Ubuntu 26.04 LTS; the default can be reconsidered when it is released.
- $g_relationship_graph_fontname
Font name and size, as required by Graphviz. If Graphviz fails to run for you, you are probably using a font name that gd PHP extension can't find. On Linux, try the name of the font file without the extension. The default value is 'Arial'.
- $g_relationship_graph_fontsize
Font size, default is 8.
- $g_relationship_graph_orientation
Default dependency orientation. If you have issues with lots of children or parents, leave as 'horizontal', otherwise, if you have lots of "chained" issue dependencies, change to 'vertical'. Default is 'horizontal'.
- $g_relationship_graph_max_depth
Max depth for relation graphs. This only affects relationship graphs, dependency graphs are drawn to the full depth. The default value is 2.
- $g_relationship_graph_view_on_click
If set to ON, clicking on an issue on the relationship graph will open the bug view page for that issue, otherwise, will navigate to the relationship graph for that issue.
- $g_graphviz_path
Requires trailing '/'. The default value is /usr/bin/
.
- $g_backward_year_count
Number of years in the past that custom date fields will display in drop down boxes.
- $g_forward_year_count
Number of years in the future that custom date fields will display in drop down boxes.
- $g_custom_group_actions
This extensibility model allows developing new group custom actions. This can be implemented with a totally custom form and action pages or with a pre-implemented form and action page and call-outs to some functions. These functions are to be implemented in a predefined file whose name is based on the action name. For example, for an action to add a note, the action would be EXT_ADD_NOTE and the file implementing it would be bug_actiongroup_add_note_inc.php. See implementation of this file for details.