Hi Paul,
If I understand you correctly, you would like the KanbanState to be updated when tasks are started and then again once all the tasks updated. This is in effect keeping the KanbanState in sync with the ScheduleState as the automated update, that Rally provides for the ScheduleState field, does its stuff.
This would seem like an obvious thing for us to implement. However, it would only apply for those situations where there is a one-to-one mapping pemissible for all states. Unfortunately, this is not the general case. It would be hard for our software to work out which KanbanState to choose if there where multiple mappings. This may be clearer if I say that a number of our customers have multiple KanbanStates mapped to the In-Progress state. Once a task is started, and the ScheduleState goes to In-Progress, we would have to make the assumption to go to the first KanbanState mapped to In-Progress - and that might not be the right one.
Due to this needing us to impose rules on workflow to implement, we have shied away from it. Implementing custom logic in this vein may require an 'active' external program that connected to webhooks - which has not yet been released for Rally. Most apps, and indeed pages, in our UI, are 'passive' in that they need human action to spur such logic software into action.
A long winded way to say that the current UI, via an app, can only update the ScheduleState from the KanbanState and not in the opposite direction.
------------------------------
Nik
Ask me a question, I'm All Ears!
Rally Sales Engineer
Rally Software
------------------------------
Original Message:
Sent: 03-23-2020 10:57 PM
From: Paul Gummo
Subject: Kanban State updates Schedule State
We have recently created a Kanban State dropdown for use on the Kanban Board app:
From the Kanban Board settings here is a partial mapping:
------------------------------
Paul Gummo
Cultivate Agile
------------------------------