AUTOMATION!
planned
Kamilla Vit
planned
Kamilla Vit
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.
E
Ernestas Miklusis
Our ambition is to have a feature to activate the individual project status when a specific task is completed. As you know, a project usually has more than one status/sub-status. Therefore, we want to automate this place, because it is not convenient to manually change the status of a project, and there is a high probability that the status will not be updated in time, which will result in a scratched report. Please let me know if more explanation is needed.
Vidas
Ernestas Miklusis can you share an example how would you define/configure which task? Maybe when all tasks completed?
B
Ben Cruttenden
Automation tools would be fantastic, I was really hoping to have items move automatically based on Due Date, or Start Date. Example being when I create an item with a due date 6 month out I put it in my Long-term row, but when the due date creeps up and is only a month away I would like it to move to my short-term row. Then when a week out it goes to my current row.
Any tips on other ways to implement this would also be great
Vidas
Ben Cruttenden: one alternative to automations could be a different way to group items, for example by due date, where due date is placed in certain periods. For example by month / by week / by how close to current date. etc. It is a different approach, but maybe it could work as well (we are considering it as part of a separate initiative to offer more grouping options).
Vidas
Merged in a post:
Automation features
M
Marco Kollster
Automatic functions like: "When I add an item in a row named "X" it automatically gets the color red" or "When moving an item to column X the item gets tag Y"
Vidas
Marco Kollster: I will merge automations request with a bigger item about the same idea so we have more upvotes. Also, I wanted to emphasize that if you need some "default" values when creating items in rows - you can set "default" template for that row. Template can contain color/tag/description or other properties. At least partially this could solve your need.
S
Sting
Another use case for automation: automatically close items that haven't been updated for a specified period of time. Closed items could be automatically archived after they have been closed for a certain period of time. These two automations would significantly declutter the workspace views.
Vidas
Sting: very valid point. Clutter is a big issue if not tackled continously.
Load More
→