AUTOMATION!
in progress
R
Richard
Congratulations on this milestone!
Like Martynas Gailius, we use child items a lot. We use them like checklist items. When we finish a task, we perform 2 actions: mark the child item as completed + change the status of the parent (for the parent to appear in the next list). If Automation could reduce this to 1 action (mark child completed), that would save time and prevent mistakes.
There are several ways to get there. The easiest would be to add an Action "Set status of parent item". (All our child items have a Tag, so by using a Tags condition, this would work. It's a workaround, but it works well.)
Another way would be to introduce something like "Checklist templates" or "Task templates"; fixed child item lists with fixed Titles. A lot more work, of course, but it would also open up a lot of other great options.
Martynas Gailius
Hi,
Really excited about this release, and congratulations for making it happen! 🤩
Our team uses child items extensively - our entire planing is based around it, so we would love to see it being included in Automations. I guess that could be tricky, because child items have unique names, but maybe something could be done with their number in line? I.e. when the child item no.3 is done > change parent items' status to <status>.
We use templates with same child items for all the products, this implementation would speed up our workflow, and reduce the number of human errors (i.e. when someone forgets to change the status and another team doesn't see that the parent item is available for later steps of the process)
I see the option to add a condition "Child items completed", but it refers to all child items, plus it can't be trigger.
Another thing we would like to point out: 50 automations / month for Premium is a ridiculously low amount. Even for Ultimate 200 / month is way too low. Automations' main objective is to reduce the amount of small tedious tasks, that a human has to do - like add tags, change statuses, lanes, add repetetive info for every item, etc. I used up half of automations just testing the feature. In the release notes it says that in the future there will be an ability to buy automations, i really hope the price will be reasonable, otherwise it's not worth it. And in my opinion base numbers included in the plans' price should be much higher.
Kamilla Vit
Martynas Gailius: Thank you for the prompt response. :)
First, I want to point out that our marketing communication about the limits wasn't clear enough, and I apologize for this miscommunication.
We count only successful runs, not automations, and the final limit of runs per account depends on the number of licenses.
So, if you have 10 licenses on the Professional monthly plan, you'll get 10 x 50 = 500 runs per month.
Kamilla Vit
Martynas Gailius: I was thinking about your case and maybe we can use 'Progress' field as a trigger? If you complete 3 childs out of 4, then Parent item progress changes to 75% automatically and can be moved to the next status.
Kamilla Vit
Hi everyone,
We’re excited to share that Automations, one of the most requested features from our community, has officially launched! 🎉
Now that you’ve had a chance to try it out, we’d really appreciate your thoughts:
• What’s working well for you?
• What could be improved?
• Are there any use cases you’d love to see supported next?
Your input helps guide our roadmap, so please feel free to share anything — big or small. Looking forward to your feedback! 🙌
Kamilla Vit
marked this post as
in progress
M
Matt Finn
Add to Automation - When I make task status to 'In progress' - make the progress percentage column for the task = '50%'
A
Annette Hopland
That would be great!
Would like to use it for:
When "status changes to In Progress", then "fill in the Start Date"
Kamilla Vit
marked this post as
planned
Kamilla Vit
marked this post as
under review
Kamilla Vit
Merged in a post:
Workflow automatization and custom fields
E
Ernestas Miklusis
It would beIt would be very cool if there was a way to automate the automatic change of the project status/sub-status (custom field) after the completion of a certain task.
Kamilla Vit
Merged in a post:
Simple automation: generating a set of tasks for all statuses
R
Richard
When creating a (parent) item, we like it to go through all the statuses and set due dates for each status, creating reminders for follow up actions.
Currently, we use a template with child items that each represents one of the statuses (the columns in the Kanban). Once a status is completed, we mark the child item and change the status of the parent item – double entry and room for mistakes.
There is already a feature request for generic automation where a similar use case is presented by another user. But, if we would create automation rules manually, it would be based on the titles of child items, which breaks down once one of the users (accidentally) changes a title of one of the child items.
Instead, the option for generating a task list (i.e. child items that can't be modified and/or are earmarked as relating to a column) based on the columns of a board would ensure a perfect matching between child items and columns, thus enables a preset automation.
It would also leave the Pandora's box of generic Automation closed, making it a lot easier to build and release. There are a few decisions to be made, like what should happen when columns are changed, but apart from that, the complexity might be fairly low.
Edit: Gitlab sort of has this kind of information. It adds and removes (status) labels when a card is moved on the Kanban and vice versa.
Load More
→