Ordering of attribute fields in a transition form

[jbostoen]

Enhancement details

Currently there is no way to specify a specific order for attribute fields in a transition form.

It defaults to inheriting some settings from the details Z-list.

Would Combodo be interested in a PR that checks if a custom Z-list exists (e.g. transition_to_<state> ) and uses that instead if present?

iTop version (if appropriate)

No response

Are you willing to create (at a later stage) a PR for that?

Yes

Additional information (if needed)

No response

[jf-cbd]

Hello, this feature sounds interesting (and we'd like this feature), but we're not sure about the best way to do it (e.g. to make it compatible with designer). I'll create a ticket since it's an evolution from XML format. Please don't create PR until we get back to you :)

[v-dumas]

'transition_to_resolved' does not fully represent a single transition, a transition is unique only if you specify the starting state and the applied stimulus. Anyhow specifying the fields order as a zlist identified by this is weird.
It sound more logical to specify it in the transition definition itself, maybe in the flags, with a new rank tag.
But we will need to specify how it would behave with a partial ranking, with mandatory field in final state not documented in the transition flags,... so a bit of thinking required.