Redmine

Well, I'm still working on this.
Anyway, let me know what you think.

+1. This would be very useful feature.

How will you define color for custom trackers?

Those should be defined by each user itself.

I have implemented the same. Maybe I could provide a patch for it.

Add related #1716.

You have interessting ideas, but they are an intensive intervention to the current design. May you create a theme and publish it on that theme list. I think we shouldn't alter the default redmine theme like this.

Do you agree to close this issue?

Filou Centrinov wrote:

You have interessting ideas, but they are an intensive intervention to the current design. May you create a theme and publish it on that theme list. I think we shouldn't alter the default redmine theme like this.

Do you agree to close this issue?

Yes indeed that finally this would be achieved using appropriate theme. The default theme may still remain not so heavy. The core idea is, currently no theme can do this right away unless Redmine provides css class per status/tracker etc. That is what this feature should achieve.

I don't think this is entirely unbelievable or a bad idea either. This issue shouldn't be closed!

Add related - #13297, #6614, #1758, #1716, #1748, #8226, #9286, #13258, #10083

The issue #13297 & #6614, #1758 talks about icons for tracker hence a dedicated css class per tracker would serve both issues.
The issue #1716, #1748, #8226 talks about style that is based on status rather than tracker.
The issue #9286 and #13258 talks about styles for highlighting priority
The issue #10083 talks about color change for resolved issues (specific status based)

One more critical thing missing in the notes of all such issues is that themes are pre-created and are not aware of available set of trackers or status. Hence, the theme should be able to provide a preset of classes and then there should be some UI way of associating them to specific

1. A defined preset 'colorization, iconized' classes that can be used. (this can be standardized)
   • preset should be sizable (say 12 - 15 styles) which all themes can implement
2. Class would define attributes under following context: (sorry if terminology is not accurate)
   • link_to_issue()
   • yellow ticket color, style, icons
   • issue context class
3. A UI window displaying { status x tracker } permutation
4. The admin can select which class to be used under what condition.
5. Styling can be used (in consistent way) when issues are listed under:
   • Issue view,
   • Issue update page,
   • Issue query page,
   • Roadmap page and on context menu
   • Gantt and Calender
   • Mypage
6. Changing theme should appropriately change appearance but shouldn't break things!

Stretching even more -¶

We can also imagine an attribute on issue e.g. issue_current_css_class which holds the value from any of the style list as possible value. If this is done, possibly (under some plugins) you can actually set the css.class as one of the fields or combination of fields reaches specific conditions.

1. if the field 'customer feedback' < Good - the issue is colored 'Red'
2. if the field 'QA Approved' - the issue is colored green.
3. Specific styling "if the task is a 'subtask' of another.
4. Issue having separate color if the issue is duplicate/ blocked by other.

I think I am stretching this issue a bit too much - but hope this ideas help simplifying and extending many styling needs fundamentally.

Can you provide a screenshot of this on the default theme?

Please take a look at the latest patch at #13747. Thanks.