View Issue Details

IDProjectCategoryView StatusLast Update
0014729mantisbtcustomizationpublic2014-09-01 21:46
Reporteraphadnis Assigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status newResolutionopen 
Product Version1.2.11 
Summary0014729: Suggestion/Feature Request: Can you offer Color Change based on user selectable Values Please?
Description

Instead of fixed color change for issues based on whether an issue is new/confirmed/resolved/Closed.... etc. Can you offer feature to change color of issues based on a user selected field and a list of values submitted by User allowing the user to select colors to change when particular values have been selected?

Additional Information

If you need more information or elaboration of my suggestion, please contact me at a_dot_phadnis_at_transasia_dot_co_dot_in OR aphadnis2002_at_yahoo_dot_com.

TagsNo tags attached.

Relationships

has duplicate 0009058 closedatrol Make color coding configurable 

Activities

aphadnis

aphadnis

2012-09-21 05:39

reporter   ~0032896

I believe this could be a very powerful feature if implemented. Initially the color change could be offered for "priority" field alone. For example.... an issue flagged as "urgent" could be displayed in RED. It could be made more generic at a later stage where a user could select any field and apply a proprietary list of flags as a drop down menu list (as is the case for tags for example)?
For example colors could be assigned on the complexity field or on the basis of projects etc.

Konzertheld

Konzertheld

2014-09-01 21:30

reporter   ~0041151

I like this idea and started to develop something. Using the following commits, you can set a config setting highlight_attribute that determines if the coloring is based on status or priority. It is extensible for other issue properties.

The colors can be changed via config, too. This was already possible for status colors and is now possible for priority colors in the same way, just set status_colors or priority_colors.

https://github.com/mantisbt/mantisbt/pull/289