Duo Chat should still be available to eligible users when working outside of their organization
Context
In the parent epic, the logic of when the GitLab Duo Chat button is shown are defined.
Problem to solve
If I normally have access to GitLab Duo Chat, but I go outside of my organization, I cannot use GitLab Duo Chat anymore:
Solution
When all of the following is true:
- User has access to Duo Chat in their org
- They are logged in, but viewing a group or project in a different org (independent of how they got access to this project/group i.e. even as a non-member if it is a public group/project)
- AI is not disabled by the admin in the group or project they are viewing
Then:
- Show the GitLab Duo Chat button
Examples:
Example | Duo Chat available? |
---|---|
User with access to Duo Chat opens a free-tier project from a different org | |
User with access to Duo Chat opens an ultimate-tier project from a different org, and AI is enabled for that project | |
User with access to Duo Chat opens an ultimate-tier project from a different org, and AI is disabled for that project |
Developer Notes:
- Please check if this other issue is resolved as part of this implementation: #438457
Rationale
- This is how it currently works in the IDE, and we want to be consistent
- We want to give users as much access to chat as possible
Edited by Juan Silva