Fix Duo Chat not answering to generic questions when disabled for group/project

CANCELLED

Closed as wontfix as with the decisions and changes that come with User experience: GitLab Duo Chat is disabled or... (&14002) this will be obsolete.

It seems that unlike as defined and unlike intended and unlike as documented, we have implemented the enterprise control somewhat quirky.

When Duo features are disabled for the group (and enforced on sub-groups), issue-, epic-, and code-pages show the following behavior:

Duo Chat button at top right is hidden (❌ not as documented and not as defined)
Duo Chat button in help menu is available (✅ as documented and as defined)
? to have code explained is not shown (✅ as documented and as defined)
When asking the chat to summarize an issue or epic error message is shown AI features are not enabled or resource is not permitted to be sent.(✅ as documented and as defined)
When asking the chat to how to create a fork the same error message is shown AI features are not enabled or resource is not permitted to be sent.(❌ not as documented and not as defined)

Assessment of bullet 1 above:

Number 1 makes a bit of sense, and we could say we keep it that way. After all users should not ask about project/group resources. When they have questions about GitLab it is somewhat more related to getting help so it makes sense that they can go through the help menu.
On the other hand it is somewhat confusing that one sees the chat in one place but not in another.
If we want to Remove GitLab Duo Chat help menu button (#457528 - closed) we should definitely change the behavior and not hide the button at the top right.
We can debate which behvior we prefer: a. just show chat in help menu b. show chat in help menu and in the top right

Assessment of bullet 2 to 4:

They make sense given that we wanted the enterprise control to focus on protecting the access to the data.

Assessment of bullet 5:

Edited Jun 12, 2024 by Torsten Linz