Hi all, what we would like to do is to have the capability to don´t let developers move a story to the open status via a transition unless there is at least one task already created.
What we did is to create an aggregate propertie that calculates the number of children (tasks) for current story. After that we wanted to use that property as a condition for the transition but we realized that you can´t select aggregates function in the "if" condition on the edit transition screen.
Do you know if we are doing something wrong or if there is another better way to do that?
Thanks in advance,
Comments
10 comments
Hi Ariel
You did not do anything wrong. Mingle currently does not support aggregate properties in the transition prerequisites (has section). Similarly it does not currently allow you to create a transition that is applicable once the value of a property is not (not set) or where the card's value is greater than some value. I think you would require these features before you could create the transition you describe.
We have these stories in our backlog and are currently planning to make some improvements to workflow in our upcoming releases. If any aspects of your request are prioritised we will update this community.
Thanks
- Suzie
Hi Suzie,
That makes sense. What about other ways to do the same? We were thinking to use MQL for creating a Card Property (Formula) that calculates the story´s number of children. If that is posible I think that property could be selected within the transition.
Thoughts?
Thanks again,
Ariel
Hi Ariel
I am afraid the same applies to the formula properties - you can not use them in transitions. In addition you can not use MQL in formula properties yet either.
I am afraid I can not think of a good way to restrict stories from being started unless tasks have been created.
As I said before we do plan on making some enhancements to workflow functionlaity and we have been using scenarios like yours to help us write and plan our stories.
Thanks
- Suzie
I want this feature also. Similar type of use case. I want to require that a particular field has A VALUE (literally, any value that is not null) before a particular transition is applicable.
Susan
As I mentioned to Ariel we do have some workflow enhancements planned but in order to see if these will meet your requirements or to understand what we would need to do to support your requirements I have a couple questions for you.
Thanks
- Suzie
Hi Suzie,
Unfortunately I didn't write down the specifics when I noted what I wanted. I was trying to create a transition for a specific card type, and the field I wanted to test was on that card. I wanted to restrict the availability of that transition to cards where the field had already been set. It was either a numeric property (like, you can't add this task to the current sprint until it has an estimate) or a tree property (like, you can't add this task to the current sprint until you've added it into the feature tree).
Hope this helps. In the future I'll take better notes when I have a new use case. :)
susan
Hey Susan
Thanks so much for that. This information certainly helps understand what you want and it seems that we have functionality currently planned for our next release that would mean you could implement the workflow you want.
Thanks again for the feedback.
- Suzie
Hi suzie,
my Use Case is pretty similar.
What I would like to do is the following: Supose that stories contain an aggregate property to count how many tasks they have. What we need is to display the transition "Development in progress" for the stories only when the aggregate is greather than 0 (We want to ensure that at least one task is created for the story).
Thanks,
Ariel
Thanks Ariel.
This feature is now available in Mingle 3.0. To read more about Mingle 3.0 please see here.
Please sign in to leave a comment.