Hey Keith,
For the one use-case you had mentioned, you may consider the Multi-Value drop-down where each team that signs off can add their name to the selected list, this will allow you to keep this approval process handled by a single field:
https://docs.ca.com/en-us/ca-agile-central/saas/create-custom-fields#multiHowever, in general, there isn't a practice to minimize custom fields, they should be created based on your needs. Normally you shall create custom fields on the Workspace level, then each team can decide if they show/hide it. Irrelevant fields for a team can be hidden and lower the count.
It sounds like there may be too much information, generally speaking (regardless of Rally) that perhaps can be reduced. Just for curiosity: How do you handle this today without Rally or outside Rally so that you don't overwhelm your teams?
Let us know if that helped. If not, perhaps you can provide more use-cases showing the need for too many custom fields.
Sagi
Original Message:
Sent: 06-07-2019 09:02 AM
From: Keith Jones
Subject: Documenting Approvals
In our world, we are expected to have several teams/individuals "sign off" on a defect or user story if it meets some particular criteria. For example, it may need to be reviewed by the data council, CAB, and/or CIO.
While this can be easily done with custom fields (Approval & Approval Date), I'm wary of having so many additional fields on a screen that I can't control.
Is anyone else dealing with these sort of workflows, that may have some brilliant workaround?
------------------------------
- Keith Jones
------------------------------