Table query showing parents without children

Follow

Comments

6 comments

  • Avatar
    Suzie Prince

    Hi Matt


    I have one suggestion. If you create an aggregate property at the 'User Task' (parent) level that is a count of stories you can easily find all "User Tasks" where count of stories < 1. You can then use this condition in card tables and MQL to get a list of User Tasks without Stories.


    E.g.


    "SELECT number, name FROM TREE 'Task' where 'story count' < 1


    Does that help?


    - Suzie

  • Avatar
    Matt Deniston

    Hi Suzie,


    That's a great suggestion... shoulda thought of that myself. Hadn't gotten into aggregate properties yet.


    I added that aggregate property to the parent in the tree, but results were a little dubious. I got an accurate story count for all 'User Task' cards that have stories, and I got an accurate count of zero for *one* of the 'User Task' cards that doesn't have any stories, and a count value of "'-" for all the remaining 'User Task' cards. When I view one of these latter 'User Task' cards, I see the aggregate properties listed below the tree information, yet the value that displays is "(not set)".


    Any ideas on what might be happening? I saw in the help that aggregate properties are calculated on the backend (asynchronously I imagine), yet I refreshed the table query on a wiki page, and the 'User Task' card itself and still get "-" and "(not set)" respectively. It's a small project (only 100 or so cards), so I'm thinking this isn't the issue.


    I tried editing the aggregate property's scope from "Story" to "All descendants" but didn't seem to have any effect on the above (since all cards under 'User Task' are stories, this scope change should have no effect... I was just fishing.


    -m

  • Avatar
    Matt Deniston

    Hi Suzie,


    I think there might be a bug the way aggregate properties are initialized or calculated. The "-" for the value of 'Story Count' for a subset of the parent cards persisted until I temporarily associated these "problem" parent cards with a story. To be clear, I literally edited a story card by setting its parent to the first parent that exhibited this problem, and then immediately set it to the next parent, and repeated until I made it through the 15 or so "problem" parents, ultimately setting the story's parent back to the appropriate one. I then refreshed the wiki page with the table query that included the 'Story Card' property and got all zeroes as expected.


    -m 

  • Avatar
    Suzie Prince

    Thanks Matt. Some of the behaviour sounds like it is expected and some does not. We are taking a look at this to see if there is a bug and will get back to you with our findings.


    In the meantime, if this is causing you problems please contact our support team who will assist you in resolving the issue.


    Thanks again


    - Suzie

  • Avatar
    Suzie Prince

    Hi Matt


    We were able to see the issue with our data. Can you please contact our support team who will assist you in resolving the issue?


    Thanks


    - Suzie

  • Avatar
    Matt Deniston

    Hi Suzie,


    As I wrote above, I figured out a workaround to get the aggregate property to be calculated and display properly on the parent cards (and thus in the table query on a wiki page). So I'm not in need of support to help resolve the issue. Cheers,


    -m

Please sign in to leave a comment.