Topic: Mingle Feature Requests / [candidate] Pie chart colors based on reporting color or configurable

We have a “Story” card type with a “Story Type” property. The Story Type property is a managed text list of “User Story”, “Refactoring” and “Defect”, with assigned Reporting colors of green, yellow and red respectively. The color choice is meant to call attention to Refactorings and Defects, in particular if we have an inordinate amount of them on a regular basis. To further comprehend this data we’ve added a pie chart to the Overview page as follows:

{{
  pie-chart
    data: SELECT 'Story Type', Count(*) WHERE Type = Story
}}

The issue is the colors for the pie slices are a canned bright red for user stories, and bright green for defects—exactly the opposite of what we wanted. It would be nice if the pie colors for charts made over a property with assigned Reporting colors used those colors.

Also perhaps a parameter syntax similar to the “series” of data-series-chart could be introduced that would allow further customization…

{{
  pie-chart
    data: SELECT 'Story Type', Count(*) WHERE Type = Story
    sectors:
    - data-point: User Story
    label: Stories
    color: green
    - data-point: Refactoring
    label: Refactorings
    color: yellow
    - data-point: Defect
    label: Bugs
    color: #990000
}}

A property value not caught by the sector declarations could revert to the existing behavior of auto picking a color.

Topic: Mingle Bug Reports / [As Designed] Card defaults not working from Add with detail...

Steps to reproduce on the Agile hybrid template’s sample project:
- Log in as an administrator.
- Project admin tab > Card properties.
- Create new card property.
- Name: “Create Date”, Property type: Date, Make property available to these card types: Story.
- Create property.
- Project admin > Card types.
- For the Story type click Edit defaults.
- Set the new Create Date property to “(today)”.
- Save defaults.
- Development Card Wall tab.
- Click Add with detail…

Expected:
- The Create Date is set to the current date.

Actual:
- The Create Date is “(not set)”.

Workaround:
- If you click “+Story” in the header the Create Date is defaulted.

Topic: Troubleshooting Installation of Mingle / Running Mingle on existing Apache (so we dont have to open ports)

Well, I gave mod_proxy_html 3.0.0 the old college try, but I’m deciding to punt. In case someone wants to pick up the torch here’s the config I had going for Mingle listening on localhost:8083 and an SSL virtual host:

# Alias Mingle's static content as this vhosts document root is somewhere else.
Alias /mingle /home/mingle/mingle/public
<Directory /home/mingle/mingle/public>
       Options Indexes FollowSymLinks
       Order allow,deny
       Allow from all
</Directory>

# Deactivate Forward Proxying.
ProxyRequests off

# Enable mod-proxy-html for the vhost.
SetOutputFilter proxy-html

# Process script tags and event attributes.
ProxyHTMLExtended on

ProxyPass /mingle/ http://localhost:8083/
ProxyHTMLURLMap http://my.host.local /mingle
<location />
       ProxyPassReverse http://my.host.local/
       ProxyPassReverseCookiePath / /
       # Use 'ce' flags as '/' is too aggressive a pattern for scripts...
       ProxyHTMLURLMap / /mingle/ ce
       # More specific script rules...
       ProxyHTMLURLMap /project /mingle/project
</location>

This got me most of the way, but mod_proxy_html was choking on some of the JavaScript as in the following example:

if (Element.visible('collapsible-content-for-Favorites')) {
  eval(new Ajax.Request('/mingle/projects/xp_template_2_0/profile/update_user_display_preference/1?user_display_preference[favorites_visible]=true', {asynchronous:true, evalScripts:true})) 
} else {
  eval(new Ajax.Re/mingle/projectprojects/xp_template_2_0/profile/update_user_display_preference/1?user_display_preference[favorites_visible]=false', {asynchronous:true, evalScripts:true}))
}

Worked for the first Ajax.Request, but mangled the second one. Character encoding issues perhaps? The mod_proxy_html FAQ warns of this possibility.

So off to setup another IP, self-signed cert, and virtual host and DNS entry. Looking forward to that fix in a future version.

~Ian