UX: Deactivating integrations with and without inheritance
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem
This is a follow up issue from #273778 (closed) to address UX around the process of "Deactivating" an integration at the Project, Group, and Instance levels.
| Instance/Group level (disabled) | Project level (disabled) | Project level (after no parent level integration) |
|---|---|---|
 |
 |
 |
Potential issues with new Reset button:
- Placement: If we add a new button, there will be 4 potential actions that can be taken [Save], [Test settings], [Reset], [Cancel]
- Terminology: the term "Reset" could imply different things depending on the context. For example "Resetting" a project that is not inheriting settings from the parent level may seem straightforward. However, "Resetting" an integration that is inheriting settings may imply either removing custom settings and reverting to the "Default" parent level settings or completely deactivating the project level integration similar to performing a "Factory reset".
Proposal
| Current | Update (UI text still pending...) |
|---|---|
 |
 |
Archive
| Options | |
|---|---|
| Current | |
| Option A |  |
| Option B |  |
Edited by 🤖 GitLab Bot 🤖