Topic: Mingle Feature Requests / [candidate] Hierarchy view usability suggestion

Hi there—

I’ve noticed that, when I have a lot of cards in a tree, the heirarchy view gets very slow to load/reload. I’ve also noticed that people often mis-click the ‘expand’ arrow, and open the card instead – meaning that they then need to click back, reload the entire page (and sometimes reset any filters they had applied to the view) ... would it be possible to make the default behaviour for each row be the ‘expand’ that the arrow provides, with a button that opens up a view similar to the card preview on the grid and tree views?

thanks!

—Andy

Topic: Mingle Feature Requests / MQL Joins

Hi there …

I’d like to be able to write queries / tables in MQL where I can use the tree structure to join data …

aggregate properties can be used as a workaround where what i’m trying to select is a sum of things limited by the parent (eg. sum of story estimates for ‘features’ with ‘priority’ of less than 4), but i don’t think they will help where i want to have conditions placed on both parent and child sets (eg. sum of ‘in development’ story estimates where their parent feature has a priority less than 4) ...

cheers!

—Andy

Topic: Mingle Feature Requests / [candidate] Where clauses in the definition of aggregate properties

It looks like this didn’t make it into 2.1, so I just wanted to add my +1

I’d like to be able to show number of unestimated stories per feature against total number of identified stories per feature – the first step for this would be to be able to caculate the count of unestimated stories as an aggregate.

thanks!

—Andy

Topic: Mingle Feature Requests / [candidate] Re-order columns in heirarchy view

Hi—

I just added a new aggregate property to a card type, and wanted to add that as a column in the heirarchy view that i had previously saved.

I’d like to be able to insert it as the 2nd column of 10 – and would like it if I didn’t have to deselect then reselect the trailing 8, but could instead drag-and-drop or otherwise reorder the display

thanks!

—Andy

Topic: Mingle Feature Requests / [candidate] Export columns to match the current view

Hi—

I’d like an option to export (to excel) just the columns that are visible, so that I can maintain my views in mingle, and not have to repeat the work of deleting/hiding irrelavent data every time i export (eg for printing)

thanks!

—Andy

Topic: Mingle Feature Requests / Auditing For Administrative Actions

+1

I’d like to be able to see who created / updated (/ deleted?) tabs and favorites

I’d also like to be able to track changes to property definitions, transitions, etc

thanks!

—Andy

Topic: Mingle Feature Requests / Combined Managed Lists as Enumerations

I’d like to be able to assign values to my managed lists, so that I can perform calculations based on them.

eg. I have ‘complexity’, ‘completeness’, and ‘volatility’ properties on stories, with values ‘high’, ‘medium’, and ‘low’ – I’d like to be able to have a formula property that defines ‘overall feature risk’ by assigning them as follows:

Low – 1

Medium – 2

High – 5

I’d like to be able to use these both ways ‘round, so that the result of a calculation could also be displayed as a text value based on it’s match with the values (and an optional operator)

eg.

Small <1>

1< Medium <4>

Large >4

thanks!

—Andy

Topic: Mingle General Discussion / Using Tags in MQL

Hi Suzie – glad I’m posing some interesting questions :)

I hadn’t thought about tags not being auditable in the same way as properties, but I don’t think this is too great an issue for us.

We’re using tags because they are cross-cutting – I can have a wiki page, a release and a set of stories that are all concerned with ‘data storage’ (for instance) – and there are times when I want to see all of those grouped together, so that they can help frame a discussion on data storage … I’d prefer to not have to go and re-key all this data in order to chart just the tagged stories (and, I can easily limit the chart to just stories by defining this in the conditions)

Further, my stories are likely to touch on multiple architectural components – and so I’d expect them to have several tags – one for each component- as far as I’m aware, it’s not possible to do ‘multi-select’ on properties … this was the primary driver for choosing tags.

We did think about using trees to do this – as really we’re just trying to overlay a different view over the same data – but again hit the limitation that you couldn’t add one story to two components …

Hope this helps explain …

Cheers!

—Andy

Topic: Mingle General Discussion / Using Tags in MQL

I have been tagging my stories with the major architectural components that they touch, and was looking to create a bar chart that had a bar for each tag, and a representation of the status of all the stories that matched that tag shown by the height of the bar (ideally as a stacked bar chart, but a ratio bar chart would do) – is this possible? I am aiming to create it without knowing each of the (potentially many) tags in advance – so something along these lines:

{{ stack-bar-chart conditions: ‘Type’ = ‘Story’ labels: SELECT DISTINCT <tag> ORDER BY <tag> cumulative: true series: – label: Complete color: green type: bar data: SELECT <tag> COUNT WHERE ‘Status’ = ‘Signed Off’ combine: overlay-bottom – label: All color: red type: bar data: SELECT <tag> COUNT WHERE ‘Status’ >=’Proposed’ combine: total
}}

thanks!

Topic: Mingle Bug Reports / Stacked bar chart ignores x-label(s)-end

Hi—I have a stacked bar chart that I’d like to use to display the changes to status over a number of iterations

I have properties that record the iteration that a status change happened, where each of these is ‘any number’- so I’m defining the chart as follows:

{{ stack-bar-chart conditions: ‘Planning Tree – Release’ = (Current Release Card) AND ‘Type’ = ‘Story’ AND ‘Iteration Added To Scope’ IS NOT NULL labels: SELECT DISTINCT ‘Iteration Added To Scope’ ORDER BY ‘Iteration Added To Scope’ x-label-start: 1 x-label-end: 40 x-label-step: 1 chart-width: 1400 chart-height: 700 plot-width: 1200 plot-height: 600 cumulative: true x-title: Iteration y-title: Total Scope series: – label: Signed Off color: green type: bar data: SELECT ‘Iteration Signed Off’, SUM WHERE NOT ‘Iteration Signed Off’ = NULL combine: overlay-bottom – label: Tested color: purple type: bar data: SELECT ‘Iteration Tested’, SUM WHERE NOT ‘Iteration Tested’ = NULL combine: overlay-bottom – label: Developed color: blue type: bar data: SELECT ‘Iteration Developed’, SUM WHERE NOT ‘Iteration Developed’ = NULL combine: overlay-bottom – label: Analysed color: orange type: bar data: SELECT ‘Iteration Analysed’, SUM WHERE NOT ‘Iteration Analysed’ = NULL combine: overlay-bottom – label: Scope color: grey type: bar data: SELECT ‘Iteration Added To Scope’, SUM combine: total
}}

However, this always shows all of the iterations for which there is data, no matter what I put as the limits for x-label (I have tried limiting it to a subset of those iterations, or iterations where there isn’t yet data (which I’d like) .. this seems to work fine for dates in the data series chart (i have properties for dates where each of the status changes happened too)

I notice that the data-series chart is documented with properties x-labels-end (with the ’s’), and have tried this as an alternative

What am I missing, or is this a bug?

thanks!

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

Great!

Not sure what happened to the alternative I mentioned in the original post – here it is again:

I’d like a view where I can have a ‘grid’ of sorts, where the parent ‘features’ are column headings (sortable, as above) and the child ‘stories’ are organized in order (by a selected property) below them

Looking forward to 2.1!

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

Hi,

I’d like to be able to sort by the columns in the hierarchy view

I’m envisaging this as the parents are first sorted by the property columns that are selected that pertain to them, with the children then being sorted within each parent according to the property columns selected that apply

For instance, I have a ‘feature’ > ‘story’ relationship, where features have a ‘priority’ and stories have a ‘priority in feature’ property, and I’d like to display the features, in priority order, with the stories within them also in their priority order

As a (better, but maybe more complex) alternative, I’d like a view where

thanks!

Topic: ThoughtWorks Studios Website Feedback / More structure around posting

Hi,

I’d like to be able to add ‘+1’ (and/or ‘-1’ or ‘suggest alternative’) posts to a feature request, so that I can add my voice in support of a feature request, without adding noise to the forums.

cheers!

Topic: ThoughtWorks Studios Website Feedback / Advanced search please

+1

and/or a way of tagging posts (eg help requests with the feature being talked about) so that others can more easily find and group related topics

cheers!

Topic: ThoughtWorks Studios Website Feedback / Advanced search please

+1

and/or a way of tagging posts (eg help requests with the feature being talked about) so that others can more easily find and group related topics

cheers!

Topic: Mingle Feature Requests / [candidate] Customizing Display

+1 Especially as it isn’t currently possible to check boxes across pages

This would also be useful if functionality by which you could drag and drop to change a scalar property (like priority) gets introduced

cheers!

Topic: Mingle General Discussion / Project variable in burn-up definition

Hi – I’m trying to write a data-series chart as follows:

{{ 
  data-series-chart 
    conditions: 'Planning Tree - Release' = (Current Release Card) AND 'Type' = 'Story' AND 'Date Added To Scope' IS NOT NULL
    cumulative: true
    x-labels-start: SELECT 'Start Date' from (Current Release Card)
    x-labels-end: SELECT 'End Date' from (Current Release Card)
    x-labels-step: 7
    x-title:  Date
    y-title:  Total Scope
    chart-height: 600
    chart-width: 700
    plot-height: 400
    plot-width: 500
    series: 
    - label: Scope
      color: black   
      type: line
      line-width: 1
      data: SELECT 'Date Added To Scope', SUM('Story Points') 
    - label: Analysis complete
      color: red
      line-width: 2
      data: SELECT 'Analysis End Date', SUM('Story Points') WHERE 'Analysis End Date' IS NOT NULL
      type: line
      trend: true
      trend-line-width: 1
    - label: Development complete
      color: orange
      type: line
      line-width: 2
      data: SELECT 'Development End Date', SUM('Story Points') WHERE 'Development End Date' IS NOT NULL
      trend: true
      trend-line-width: 1
    - label: QA complete
      color: yellow
      type: line 
      line-width: 2
      data: SELECT 'QA End Date', SUM('Story Points') WHERE 'QA End Date' IS NOT NULL
      trend: true
      trend-line-width: 1
    - label: Accepted
      color: green
      type: line
      line-width: 2
      data: SELECT 'Signed Off Date', SUM('Story Points') WHERE  'Signed Off Date' IS NOT NULL 
      trend: true
      trend-line-width: 1
}}

... the problematic lines being, of course:

x-labels-start: SELECT 'Start Date' from (Current Release Card)
x-labels-end: SELECT 'End Date' from (Current Release Card)

... because the ‘from’ is implicitly ‘all cards’ (and I can’t think of an equivalent ‘where’)

does anyone have a work-around for this, or will I have to wait the whole week until 2.1 is released? ;)

cheers!

—Andy

Topic: Mingle General Discussion / new iteration

Hi Cambazz

Do you mean that you simply want different tabs with different iterations shown? In which case, you just need to create a filter (on the right hand side) that displays the information, then ‘save as favorite’, then go to the ‘manage favorites and tabs’ link (at the bottom of the favorites), and click on the ‘make tab’ link, next to your saved filter.

For the project I’m on, we’ve also set up project variables, for ‘this iteration’, ‘next iteration’ and ‘last iteration’ – we’ve then used these in our tabs/filters, and so, as time progresses, we can change the views by changing the variables, without having to update each of them seperately.

Hope this helps

—Andy

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

I was wondering the same—a couple of other scenarios you may wish to consider:
1) Linking risks to (mitigating) stories
2) Linking stories to stories they are dependent on
note that in both these cases, there may be multiple values for which the link holds