Bonjour
Il serait pratique de pouvoir organiser les vues dans le menu du projet. En effet, lorsque le nombre de vues partagées (ou même privées) est important, la lisibilité n'est plus assurée.
Plusieurs pistes/suggestions :
- pouvoir ajouter des séparateurs/titres (comme dans les cartes par exemple) pour répartir les vues selon le besoin adressé
- pouvoir organiser les vues de façon hiérarchique sous forme d'arbre

Exemple de besoin :
Un projet itératif faisant intervenir plusieurs phases macros (réalisation, validation par exemple). On peut définir 3 vues : une vue "itération" permettant de gérer le contenu de l'itération, une vue "réalisation" permettant de gérer les étapes de développement, et une vue "validation" permettant de gérer les étapes de validation d'une itération. D'autres vues peuvent être présentes et indépendantes de cette notion d'itération.
Il y aurait un sens ici à définir la vue "itération" comme parente des vues "réalisation" et "validation" (d'une point de vue lisibilité).

Hello.
It would be amazing to start to work on a card and, on a task (or subtask, sub-sub task and so on), be able to count the time without having the need of manually log the information.
I know that there is a feature in which, if you right click the checkbox, you can mark the task as "In progress", so, wouldn't it be amazing if marking the checkbox as "In progress" triggers a time counter?(Similarly, pausing the task the same way would pause the counter and, by marking in progress again, the time counter would continue from where it was stopped)
Moreover, the total time spent should appear somewhere on the parent card/task itself, I'll give an example below:

CARD
Task 1
Task 2

Subtask 1

Subtask 2

Subtask 3

Subtask 4

Task 3

Now, let's imagine that I've worked on the card and all the tasks are now completed, with each time counted by this automated (possibly) new feature:

CARD (00:20:50)
Task 1 (00:03:01)
Task 2 (00:14:24)

Subtask 1 (00:02:51)

Subtask 2 (00:00:47)

Subtask 3 (00:07:21)

Subtask 4 (00:03:25)

Task 3 (00:15:30)

This would be amazing!
Now, the Task 2 used as example is a sum of all the times contained in its subtasks (and that makes sense, because when you work on a subtask and, eventually, complete all subtasks, the parent task is now complete as well); this can be tricky to develop, as the task has to detect that it has subtasks and sum all it's subtasks time counters.
Similarly, the Card time counter is a sum of all its tasks, by the same reason said before.

Please, implement this! I cannot wait to see how the reports would look like, like the time spent on a project where you can see the time spent on each card, tasks, subtasks, sub sub tasks and so on

You can contact me by e-mail if you need more details and even help with the implementation/testing this feature if it gets approved

Thank you so much!

It's possible today to define an automated action for a card when moved to a defined group.

But, it's not possible to do it when an attribute takes a precise value.

It would be very appreciated to be able to define automated actions when changing the value of an attribute.

Better : be able to define automated actions based on "trigger" type attribute (KQL based expression type returning TRUE for example)

For example :
I have a card with a ROI field formula calculated from a business value and story points.
I would like to have a "trigger" type attribute which defines :
- the condition for trigger (for example : ROI < 10)
- the action to perform (for example : move to a group "Not interesting")

Thanks :)