[go: up one dir, main page]

Skip to content

Configure integration fields based on license

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

For some integrations, certain settings should only be available with a specific license.

Examples:

  • The Vulnerability events for chat integrations added in !65245 (merged) should only be available in Ultimate.
    • For now we're still showing the field with a comment about the license, but the setting doesn't actually do anything unless the license is present.

Proposal

  • Extend the backend to specify if a field requires certain tiers (maybe by adding new attributes to Integration#fields).
  • Extend the frontend to hide or disable these fields if the necessary license isn't present.

Background

The following discussion from !65245 (merged) should be addressed:

  • @balasankarc started a discussion: (+8 comments)

    @toupeira This was the only easy way we could think of to ensure Vulnerability option is not shown to users who aren't on Ultimate. I hope the comment above makes it clear why it had to be a selective removal instead of a selective insertion. WDYT?

Edited by 🤖 GitLab Bot 🤖