GitLab issueshttps://gitlab.com/gitlab-org/gitlab/-/issues2019-08-12T15:52:01Zhttps://gitlab.com/gitlab-org/gitlab/-/issues/2485Deploy boards won't stop spinning on 9.2.1-ee2019-08-12T15:52:01ZMark PundsackDeploy boards won't stop spinning on 9.2.1-eeI updated i2p.online to 9.2.1-ee and the deploy boards don't render anymore. They just keep spinning.
![image](/uploads/9c0c60bcc08abf22993ae4f44497a560/image.png)
```
main.56b5e32c3748e858c780.bundle.js:11
TypeError: Cannot read prop...I updated i2p.online to 9.2.1-ee and the deploy boards don't render anymore. They just keep spinning.
![image](/uploads/9c0c60bcc08abf22993ae4f44497a560/image.png)
```
main.56b5e32c3748e858c780.bundle.js:11
TypeError: Cannot read property 'getDeployBoard' of undefined
at t.value (environments.6bf7fa0fb47d549dc6e0.bundle.js:1)
at r.created (environments.6bf7fa0fb47d549dc6e0.bundle.js:1)
at pe (main.56b5e32c3748e858c780.bundle.js:11)
at r.JTVE.e._init (main.56b5e32c3748e858c780.bundle.js:11)
at new r (main.56b5e32c3748e858c780.bundle.js:11)
at Le (main.56b5e32c3748e858c780.bundle.js:11)
at init (main.56b5e32c3748e858c780.bundle.js:11)
at r (main.56b5e32c3748e858c780.bundle.js:11)
at a (main.56b5e32c3748e858c780.bundle.js:11)
at f (main.56b5e32c3748e858c780.bundle.js:11)
```
/cc @filipa @grzesiek9.2Luke BennettLuke Bennetthttps://gitlab.com/gitlab-org/gitlab/-/issues/1976Re-word Board to Boards in navigation2022-05-19T16:54:16ZVictor Wuvictor@gitlab.comRe-word Board to Boards in navigation### Resources
FE @lbennett
### Description
In EE we have multiple boards. Our nav should reflect that.
I thought we had an issue for it, or maybe it was in some nav issue and got lost.### Resources
FE @lbennett
### Description
In EE we have multiple boards. Our nav should reflect that.
I thought we had an issue for it, or maybe it was in some nav issue and got lost.9.2Luke BennettLuke Bennetthttps://gitlab.com/gitlab-org/gitlab/-/issues/1526Suggest approvers in merge request - UX improvements2022-05-19T16:57:29ZVictor Wuvictor@gitlab.comSuggest approvers in merge request - UX improvements### Resources
PM @victorwu | FE @lbennett
### Problem
* In the existing implementation, the suggested approvers is below the entire section. It is not that helpful when you are actually choosing approvers.
<img src="/uploads/b550415ce3...### Resources
PM @victorwu | FE @lbennett
### Problem
* In the existing implementation, the suggested approvers is below the entire section. It is not that helpful when you are actually choosing approvers.
<img src="/uploads/b550415ce3323b089384da23854e3d89/Screen_Shot_2017-01-16_at_09.39.07.png" height="300px" />
* The new design of approvers selection (per project, and per merge request), is here: https://gitlab.com/gitlab-org/gitlab-ee/issues/1738
* This issue will also help with the selection of approvers themselves: https://gitlab.com/gitlab-org/gitlab-ee/issues/1593.
### Scope
* Re-design the UX of the suggested approvers to be inline with the above new design.
* The suggestion BE algorithm itself does not change. The scope of this issue is just integrating that suggestion on the FE in a coherent manner.
* The BE algorithm to change suggestions will be worked on in separate issues.
- This applies to the project settings area. The same area in the merge request web form should also be updated, but is a stretch goal for this issue. (I.e. if it's minor extra effort and can be done together easily without delay, let's include it as well.)
### Design
<img src="/uploads/71fd57a3bc57d6d6b0f95d8e4dfcffe4/Screen_Shot_2017-03-19_at_6.28.26_PM.png" width=70% />
`Add an approver / a group as an approver suggestion for each merge request` was replaced by `Suggested approvers: Username`.
![suggested-approvers](/uploads/3b44b650b52f5ab377cf8f17f795fb86/suggested-approvers.png)9.2Luke BennettLuke Bennett