Add doc page for project-level Issue Analytics
What does this MR do?
Project-level Issue Analytics was introduced after group-level Issue Analytics, with documentation that simply pointed to the original group-level documentation. That caused the documentation to be more complex than it needed to be, and also caused the documentation left- nav to behave incorrectly. This introduces a separate page for the project-level feature to fix these problems. This also removes some content from the group-level documentation that only applied to the project-level feature.
This was originally motivated by an issue about the documentation nav links being jumpy. This is similar to a concurrent MR to add documentation page for group-level VSA.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
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
Related to #270216 (closed)