Skip to content

Active integrations should be displayed in a separate table

What does this MR do?

Implements #214885 (closed) - split the Integrations table into 2 tables - active and inactive.

We have moved the table from HAML to Vue - this is somewhat of a pre-optimisation that will enable us to do things like filter the table, etc. in the future.

Screenshots (strongly suggested)

Small Big
Screen_Shot_2021-03-25_at_3.05.40_pm Screen_Shot_2021-03-25_at_3.05.26_pm
Project Group Admin
Screen_Shot_2021-04-12_at_4.49.41_pm Screen_Shot_2021-04-12_at_4.50.02_pm Screen_Shot_2021-04-12_at_4.50.17_pm

Empty states

No active integrations Every integration activated
Screen_Shot_2021-04-12_at_4.57.01_pm Screen_Shot_2021-04-12_at_4.58.07_pm

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by Tom Quirk

Merge request reports

Loading