Topic: Mingle Bug Reports / Time out when generating chart

How can I avoid the problem below that is reported when creating a stack-bar-chart?

Error in stack-bar-chart macro: Timeout::Error: execution expired: SELECT DISTINCT `cp_sprint_number`.value AS `Sprint Number`, order_by_cp_sprint_number.position IS NULL, order_by_cp_sprint_number.position FROM router_cards LEFT OUTER JOIN enumeration_values AS order_by_cp_sprint_number ON lower(order_by_cp_sprint_number.value) = lower(router_cards.cp_sprint_number) AND order_by_cp_sprint_number.property_definition_id = 59

LEFT OUTER JOIN enumeration_values AS `cp_sprint_number` ON lower(`cp_sprint_number`.value) = lower(router_cards.cp_sprint_number)
    AND `cp_sprint_number`.property_definition_id = 59
 ORDER BY order_by_cp_sprint_number.position IS NULL, order_by_cp_sprint_number.position   Help

The Help link does not really help. It points to http://studios.thoughtworks.com/mingle/2.0.1/help/macro_and_mql_guide.html, but that page does not say what I can do to avoid time outs.

Topic: Mingle Bug Reports / [As-designed] Project variables are not included in all value lists for properties

Context: Mingle 2.0.1. I have a card property ‘Sprint number’. I have a project variable (Current sprint number). The project variable is configured to show up in value lists for the ‘Sprint number’ property.

Problem description: (Current sprint number) is included in value list for ‘Sprint number’ in filters and when editing transitions. It is not included in the value list that appears when clicking on the ‘Sprint number’ property on a card. And it is not included in the value list that appears when a transition is executed that requires user input for ‘Sprint number’.

I believe that this problem did not exist in Mingle 2.0, so I think this is a regression.

Topic: Mingle General Discussion / [question] How do I link cards together?

Jake,

“Card trees” is the feature and it was added to Mingle 2.0. It is documented in http://studios.thoughtworks.com/mingle/2.0.1/help/working_with_card_trees.html

Topic: Mingle Feature Requests / [candidate] Query with 'Relationship property' card number

Jake,

This suggestion was already included in http://studios.thoughtworks.com/discussion/forums/1/topics/611 and you already commented on it :-)

Topic: Mingle Bug Reports / [Fixed] value queries for a property do not work while table queries do

Adam,

Maybe you should tag this discussion with [Fixed], because it is indeed fixed. I verified it with Mingle 2.0.1.

Thanks.

Topic: Mingle Bug Reports / [Fixed-2.1] Unable to select a card from a card list when the name includes double quotes

Context: I have sprint cards. I have a project variable called ‘Current sprint’, which holds a card. I have a sprint with a name that includes double quotes.

Scenario: I want to change the value of the project variable ‘Current sprint’. In the ‘Project variables’ page, I click ‘Edit’ to edit the project variable. In the “Edit project variable” page that appears, I click on the linked value of the project variable. A dialog appears, asking me to “Select card for Sprint”. When I click on a sprint that has double quotes in the name, nothing happens.

Workaround: when I remove the double quotes from the name of the sprint card, clicking on it in the “Select card for Sprint” dialog sets the value of the project variable.

I did not try this with other “strange” characters, such as single quotes.

Topic: Mingle Feature Requests / [candidate] Make deleting cards easier where card trees are involved

+ 1

Topic: Mingle General Discussion / Does Mingle scale well?

My team uses Mingle since October last year and currently we have 1016 cards in our project. Since a few weeks, in which we created many cards, we have seen more and more scaling issues. I will bring examples to the Mingle user meeting next week, but I like to use this forum to investigate whether other teams suffer from the same performance problems that we see.

We have the feeling that the more cards we add, the slower Mingle becomes. There is already a discussion in http://studios.thoughtworks.com/discussion/forums/7/topics/595 about the unresponsive script, and I just posted a performance problem with the hierarchy view (in the bug forum).

My concern is that Mingle may not scale well. If it does not, it will become a serious risk for my team’s project. So I like to start a discussion and collect feedback that TW can use to improve any scaling issues we experience. So:

• Do you see the same performance problems we have?
• Do you have other performance problems?
• How many stories do you have in your Mingle project?
• How many trees?

Thanks for any feedback.

Topic: Mingle Bug Reports / Performance problem in hierarchy view

In our Mingle 2.0 project, we currently have 1016 cards. All the cards are at least in one card tree. Currently the card tree has 5 cards at the highest level. When I open a hierarchy view on that card tree, it takes 27 second before FireFox 2.0.0.14 on Windows XP is ready with loading the page. Because my team members access that view many times a day (because we are populating the tree with cards), they experience this slow loading as very annoying. My impression is that the more cards we add to the project, the longer it takes, but I have no objective evidence of that.

Because this problem is bothering us daily, I ran a profile with FireFox while refreshing the web page with the hierarchy view. The results are below. I only included the rows of the profile report that show a percentage higher than 0%. If you like I can send the full profile report in Excel format.

Function    Calls    Percent    Own Time    Time    Avg    Min    Max    File
$    1016    47.50%    2671.76ms    2687.385ms    2.645ms    0ms    15.625ms    base_8287.js (line 104)
clear    9821    17.22%    968.702ms    2749.873ms    0.28ms    0ms    2062.407ms    base_8287.js (line 64)
intersect    1671    5.56%    312.487ms    312.487ms    0.187ms    0ms    296.862ms    base_8287.js (line 65)
mixin    3230    2.78%    156.243ms    6499.71ms    2.012ms    0ms    2062.407ms    base_8287.js (line 283)
collect    2531    2.50%    140.618ms    343.735ms    0.136ms    0ms    124.995ms    base_8287.js (line 53)
inGroupsOf    4919    2.50%    140.618ms    2921.74ms    0.594ms    0ms    2062.407ms    base_8287.js (line 57)
inGroupsOf    895    2.22%    124.995ms    124.995ms    0.14ms    0ms    62.497ms    base_8287.js (line 57)
clone    22049    1.94%    109.37ms    109.37ms    0.005ms    0ms    15.625ms    base_8287.js (line 36)
mixin    806    1.67%    93.746ms    6702.824ms    8.316ms    0ms    3609.213ms    base_8287.js (line 855)
eachSlice    1616    1.11%    62.499ms    578.101ms    0.358ms    0ms    296.862ms    base_8287.js (line 51)
extend    3431    1.11%    62.497ms    62.497ms    0.018ms    0ms    15.625ms    base_8287.js (line 30)
mixin    809    1.11%    62.497ms    6624.703ms    8.189ms    0ms    2078.031ms    base_8287.js (line 283)
aliasMethodChain    3230    1.11%    62.497ms    62.497ms    0.019ms    0ms    15.625ms    base_8287.js (line 284)
$A    2416    1.11%    62.497ms    62.497ms    0.026ms    0ms    15.625ms    base_8287.js (line 61)
clone    9821    0.83%    46.873ms    46.873ms    0.005ms    0ms    15.625ms    base_8287.js (line 36)
setParent    806    0.83%    46.873ms    46.873ms    0.058ms    0ms    15.625ms    base_8287.js (line 856)
aliasMethodChain    3230    0.83%    46.872ms    109.369ms    0.034ms    0ms    15.625ms    base_8287.js (line 284)
partition    24    0.56%    31.25ms    31.25ms    1.302ms    0ms    15.625ms    base_8287.js (line 59)
_text    122    0.56%    31.249ms    46.873ms    0.384ms    0ms    15.625ms    base_8287.js (line 11)
inGroupsOf    3230    0.56%    31.249ms    31.249ms    0.01ms    0ms    15.625ms    base_8287.js (line 57)
node    146    0.56%    31.249ms    93.746ms    0.642ms    0ms    15.625ms    base_8287.js (line 1)
(no name)    1    0.56%    31.249ms    6952.814ms    6952.814ms    6952.814ms    6952.814ms    cards (line 27343)
clear    4906    0.56%    31.248ms    2952.988ms    0.602ms    0ms    2062.407ms    base_8287.js (line 64)
clone    4342    0.28%    15.625ms    15.625ms    0.004ms    0ms    15.625ms    base_8287.js (line 36)
emptyFunction    1030    0.28%    15.625ms    15.625ms    0.015ms    0ms    15.625ms    base_8287.js (line 20)
_createNotSetFilterGroupElement    6    0.28%    15.624ms    15.624ms    2.604ms    0ms    15.624ms    base_8287.js (line 772)
inGroupsOf    1616    0.28%    15.624ms    593.725ms    0.367ms    0ms    296.862ms    base_8287.js (line 57)
include    280    0.28%    15.624ms    15.624ms    0.056ms    0ms    15.624ms    base_8287.js (line 48)
getInputs    2    0.28%    15.624ms    15.624ms    7.812ms    0ms    15.624ms    base_8287.js (line 240)
inGroupsOf    9883    0.28%    15.624ms    2765.497ms    0.28ms    0ms    2062.407ms    base_8287.js (line 57)
setOpacity    13    0.28%    15.624ms    15.624ms    1.202ms    0ms    15.624ms    base_8287.js (line 137)
observe    36    0.28%    15.624ms    15.624ms    0.434ms    0ms    15.624ms    base_8287.js (line 597)
removeOption    12    0.28%    15.624ms    15.624ms    1.302ms    0ms    15.624ms    base_8287.js (line 735)
clone    542    0.28%    15.624ms    15.624ms    0.029ms    0ms    15.624ms    base_8287.js (line 36)
initialize    6    0.28%    15.624ms    187.492ms    31.249ms    31.248ms    31.249ms    base_8287.js (line 775)
initialize    6    0.28%    15.624ms    156.243ms    26.04ms    15.624ms    31.249ms    base_8287.js (line 775)
fireContentLoadedEvent    1    0.28%    15.624ms    7280.924ms    7280.924ms    7280.924ms    7280.924ms    base_8287.js (line 274)
expandWithPrefetch    806    0.28%    15.624ms    31.248ms    0.039ms    0ms    15.624ms    base_8287.js (line 861)
calculateHowManyPixelsPerEm    1    0.28%    15.624ms    31.248ms    31.248ms    31.248ms    31.248ms    base_8287.js (line 1407)
_rememberLastRowsNumber    1    0.28%    15.624ms    15.624ms    15.624ms    15.624ms    15.624ms    base_8287.js (line 1410)

Topic: Mingle Bug Reports / Different rendering of table query result in preview and after saving

I have 40 Sprint cards that are also part of a tree Release > Sprint > Story. I have a wiki page with a table that lists the sprints and some of their properties:

{{table query: select  'Sprint number', Name, 'Start date', 'End date', Goals, 'Sprint effort', 'Available mandays', 'Number of cards', Number where Type = Sprint order by 'Start date' desc}}

The card properties used in the table query are ‘Sprint number’,’Name’, ‘Start date’, ‘End date’, ‘Goals’, ‘Available mandays’, ‘number’. The aggregate properties used in the table query are ‘Sprint effort’ and ‘Number of cards’.

Scenario: I changed the name of a sprint card and then I refreshed the wiki page in my web browser (FireFox 2.0.0.14 on Windows XP). The new name was not listed, but the old one was. When editing the wiki page and turning on the preview, the new name was shown. After saving the wiki page shows the old name instead of the new name.

Maybe this is related to http://studios.thoughtworks.com/discussion/forums/7/topics/599, but even after 1 hour the old name is still shown on the wiki page, while the preview shows the new name of the sprint card. Opening the wiki page in a new browser window does not change the situation.

Topic: Mingle Bug Reports / [Fixed] Grid view locks up with "unresponsive script" error msg

More colleagues start seeing this problem. Always in a hierarchy view. Is it possible that the more cards we have in Mingle the more we see the problem? We have created many stories the past few weeks and certainly this week. A few weeks ago, we never saw the problem.

We are using mingle_unix_2_0_8540.

Topic: Mingle Bug Reports / Slow updates of tables and charts after creating cards and changing card property values

David,

I changed the value from 20 to 5 this morning. The change seems to have no impact. In one instance I waited more than 1 minute before a table was up-to-date.

Topic: Mingle Feature Requests / Project variables and date literals in formula properties

As documented on http://studios.thoughtworks.com/mingle/2.0/help/formula_property_examples.html, it is possible to define a formula property using integer literals, such as:

("Start Date" - "End Date") / 7

I tried to create a formula property that contains a date literal, like

"Creation date" - "10/15/2007" / 14 + 1

But Mingle does not support date literals in formula properties. It responds with an error message:

The formula is not well formed. No such property: 10/15/2007.

So I tried something else. I created a project variable called “First day of first sprint”, a date set to 10/15/2007, and then I tried creating the formula property:

"Creation date" - ("First day of first sprint") / 14 + 1

The formula is not well formed. No such property: First day of first sprint.

So, my conclusion: (1) date literals are not allowed in formula properties, (2) using project variables in formula properties is not allowed. Besides not serving my purpose, I think this behavior is inconsistent with queries for tables and charts, where date literals and project variables can be used.

Topic: Mingle Feature Requests / shared wiki pages

Shared wiki pages would be very nice in my development group, where different scrum teams use Mingle and their projects are modeled as different projects in Mingle. Shared wiki pages could be very useful to collect information that is useful for all developers and other users. One wiki page I would introduce if Mingle supported shared wiki pages is “how to use Mingle in our development process”. Another would be a dashboard with the progress of every project.

Topic: Mingle General Discussion / How to use relationship properties in where clauses of queries?

Thanks Suzie.

Referring to the number instead of the name makes sense, because the name may change while the number does not change. I would not like having to change all the queries that use the name when the name changes.

Topic: Mingle General Discussion / How to use relationship properties in where clauses of queries?

I have a problem and I cannot find the solution in http://studios.thoughtworks.com/mingle/2.0/help/mql_reference.html. I also looked in http://studios.thoughtworks.com/mingle/2.0/help/macro_reference.html under “Markup value query”, but the text says: “Source file topics/markup_value_query.xml missing.”

I have feature cards and epic cards. I have a tree Epic > Feature. The tree is called “Scope” and the relationship property is called “Scope – Epic”. I like to express queries about features in the context of their epic. For instance, if I like to count the feature cards associated with an epic card with number 796, I would expect to write it like this:

{{value query: select count(*) where type = feature and 'Scope - Epic' = 796}}

But that does not work. How do I refer to a card as a value for “Scope – Epic”?

Topic: Mingle Bug Reports / [Fixed] Grid view locks up with "unresponsive script" error msg

I have a reproducible scenario for this error message in a hierarchy view.

I open a new tab in FireFox 2.0.0.14 on Windows XP. I log in and click a favorite view. It is a hierarchy view.

The hierarchy view lists 2 cards. When I expand the second one, 15 cards appear below it. When I then click the first one, I expect that 4 cards appear below it. Sometimes the child cards do not appear and the browser shows a message box titled “Warning: unresponsive script”. Sometimes, the child cards appear, but when I collapse the first (and just opened) card, the message box is shown. After some experimenting, it seems that the speed at which I expand and collapse the two cards determines the appearance of the message box at expand or collapse time.

After some more testing, I can now also reproduce the problem by expanding the first card, expanding the second card and collapsing the second card again.

There is a small time span between clicking the triangle for expanding/collapsing and the appearance of the message box. In that time span, the mouse pointer in the form of a hand with a pointing finger does not change, wherever I move it in the browser. That is an indication for me that the problem will happen.

Interestingly, I cannot reproduce it when I enable Firebug.

I have not yet experienced the problem when expanding and collapsing cards at other levels than the top level of the hierarchy.

I hope this helps in tracking down the bug.

Topic: Mingle Feature Requests / [candidate] Transitions that apply to a selection of card types

Use case: I have card types “story”, “task”, “bug” and “risk”. For the first 3 card types, I like to have a transition “Set to complete”, which sets property “Status” to “Complete” and property “Completion date” to “(today)”. Card type “risk” does not have properties “Status” and “Completion date”, so my desired transition does not apply for risk cards.

In Mingle 2.0, when I create a new transition, I have to select a card type. For the use case above, I have the choice between “(any)” and the 4 card types “story”, “task”, “bug” and “risk”. When I select “(any)”, no properties are available for the transition, because not all card types share the same properties. When I select “story”, “task”, or “bug”, I can set the transition values of the properties, but to make the transition apply to the 3 cards types, I have to create 3 transitions. On top of that, I cannot give the transitions the same name. Consequently, I would have 3 transitions: “Set story to complete”, “Set task to complete” and “Set bug to complete”. This is not desirable. It results in many transitions that differ only in the card type. And it is confusing for the users, because depending on the card they select, they see transitions with other names, while the semantics of the transitions is the same.

What I like to have is the possibility to create 1 transition called “Set to complete” for the 3 card types “story”, “task” and “bug”. If Mingle would allow me to make a selection of card types, rather than requiring me to select only one, that would help me a lot.

Topic: Mingle Bug Reports / [As Designed] Component property ?

Suzie,

Creating formula properties using card properties works fine. Example: I have a “Risk” card type with properties “Risk impact” and “Risk probability”, both numbers. I have a formula property “Risk priority” which is defined as ‘Risk Probability’ * ‘Risk Impact’.

Thanks for starting a discussion in http://studios.thoughtworks.com/discussion/forums/6/topics/606 to ask for more use cases of formulas with aggregate properties.

Topic: Mingle Feature Requests / [implemented-2.1] Sorting in hierarchy view

Suzie,

In my posts and in the title of this topic, I should have written “hierarchy view” instead of “tree view”. Maybe you can change the title?

Sorry for the confusion.

Topic: Mingle Bug Reports / [Fixed] Grid view locks up with "unresponsive script" error msg

Sorry, I meant: I saw it in the hierarchy view, not the tree view.

Topic: Mingle Bug Reports / [Fixed] Grid view locks up with "unresponsive script" error msg

I have seen it multiple times in the tree view as well, also on Win XP and FireFox 2.0.0.14. I do not have a reproducible scenario though.

Topic: Mingle Bug Reports / Slow updates of tables and charts after creating cards and changing card property values

Thanks for the answer Dave.

What is the lowest value you recommend? If I would lower it to 1 second, what would be the impact on the responsiveness of Mingle?

Topic: Mingle Feature Requests / [implemented-2.1] Sorting in hierarchy view

Suzie,

No, it does not extend to other views, which makes it different from the discussion you refer to. I see it more as a matter of consistency. In the list views, it is possible to click a column header to sort the view. In the tree view, that functionality is not present. That makes the two views inconsistent.
I guess implementing sorting on any column should be easy, because Mingle already does it on the number column column today.

Of course, if Mingle would support ordered lists as suggested in http://studios.thoughtworks.com/discussion/forums/6/topics/75 and that order could be applied to a tree view, I would be able to make an ordered list for the top-level cards in a tree view and that would solve the problem I currently face. But introducing ordered lists and allowing to apply them in different views would make Mingle more complex. Supporting sorting in the tree view is far less intrusive.

Topic: Mingle Feature Requests / [implemented-2.1] Sorting in hierarchy view

Now tree views sort cards on card number, level by level. I am using a tree view to view release cards and sprint cards. I like the release cards to be sorted on other criteria (the name for instance) rather than the card number. Now, if I create a release card for a release that logically comes before a release represented by an existing release card, Mingle will show it in an order that is not the logical order, which makes it hard for readers to understand the tree view.