Skip to content

Feature request: Allow for bulk removal of custom integration settings

Proposal

Presently, group owners must manually remove custom integration settings from a group's projects. Not an issue for groups with a handful of projects. However, it's a big chore when a target group has many subgroups and, say, 100 projects.

Proposal: Add admin config option to allow group owners to remove custom settings from their groups' subgroups and projects.

EDIT:

Here is the inciting experience from a customer:

We started with "Custom issue Tracker" to integrate with TFS [Team Foundation Server]. Now, switched to "Jira" integration (required to hyper link jira issue id) along side webhooks (updates jira issue with commit details). When I enabled, Jira issue tracker at group level that has multiple nested sub groups totaling of 1350+ projects. Even though we removed/reset  "Custom issue tracker" at group level, It still remembers this integration setting at each sub-group and project level, irrespective of whether or not any settings override at sub-group or projects. It also says using default settings (inherited, all entries greyed out at subgroup/project level) We don't override at sub-group or project level for 95% times. When a new commit is made, it will hyper link all the jira issues to TFS (old custom integration that is still disabled/removed at top group level. Solution is to manual navigate to each project and delete the custom issue tracker integration to make it work. 

even after removing at each project level, "custom issue tracker" integration still shows up at sub groups with "checked" mark along with Jira. There is no way to delete at sub-group level using api [which would be a preferable/less tedious alternative]

Edited by Christopher Ramos
OSZAR »