Cleanup orphaned issue boards sidebar components
What does this MR do?
Working toward resolving the last remaining vestiges of vue templates defined in HAML from the legacy issue boards sidebar (#321095 (closed)). This MR removes a bunch of dead code. A future MR will refactor the issue board SPA to no longer rely on the vue runtime template compiler within /app/views/shared/boards/_show.html.haml
, app/assets/javascripts/boards/index.js
, and ee/app/assets/javascripts/epic_boards/index.js
.
How to setup and validate locally (strongly suggested)
Visit an issue boards or epic boards page and interact with the sidebar that appears when clicking on an item. It should behave the same both with and without the changes in this branch.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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