It would save administrative burden if there were an option when creating a field to either add it to all workspaces or add it to none.
When adding a new field to a backlog item or portfolio item in Agility, the current behavior is that it is automatically added to all workspaces. If it's not needed on all workspaces, then it has to be removed from the others. This is administrative headache and runs a risk that users on a different workspace will start using the field when they shouldn't. In cases like ours where we have hundreds of workspaces, this is significant administrative overhead with a decent risk that the person doing it will miss removing the field from somewhere.
The current behavior is in contrast to multi select or dropdown fields, which default to having no list values added. You have to go into each workspace to add them. This is better behavior, because it reduces the risk that someone will use a list value that they shouldn't.
There are cases where adding a field to all workspaces is a better option, so giving someone the choice when they add the field makes sense. If making that optional isn't feasible, changing the default to not add it to all workspaces would ease administrative burden and reduce risk of bad data.
by: Andy L. | 12 days ago | Administration
Comments
Great feedback.. We haven't heard this feedback from other customers. Most cases, customers wanted to add the field by default to all the workspaces so that the admin over ahead will be lot lesser to go and enable to each workspace. btw.. did you try the new workspace, we will have an option to select all workspaces then enable/disable the specific field easily. Select all workspaces will be available in couple of weeks time.