GitLab FOSS issueshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues2019-08-07T08:26:45Zhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/42900Fix warning messages for milestone promotion and label promotion2019-08-07T08:26:45ZVictor Wuvictor@gitlab.comFix warning messages for milestone promotion and label promotionThese are the current warning messages. They are incorrect:
<img src="/uploads/0e3d4d3e8df1ad12262d22abd4c2b4c3/Screen_Shot_2018-02-08_at_15.01.14.png" height="200px" />
<img src="/uploads/a579f06b3ed363238155a4c0688a5fb0/Screen_Sh...These are the current warning messages. They are incorrect:
<img src="/uploads/0e3d4d3e8df1ad12262d22abd4c2b4c3/Screen_Shot_2018-02-08_at_15.01.14.png" height="200px" />
<img src="/uploads/a579f06b3ed363238155a4c0688a5fb0/Screen_Shot_2018-02-08_at_15.03.35.png" height="200px" />
### Warning messages to implement in this issue
>>>
Promoting [milestone] will make it available for all projects inside [Group name]. Existing project milestones with the same name will be merged. This action cannot be reversed.
Promoting [label] will make it available for all projects inside [Group name]. Existing project labels with the same name will be merged. This action cannot be reversed.
>>>10.5Jose Ivan VargasJose Ivan Vargashttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/42545Milestone Quick Action not displayed with no project milestones but with grou...2019-08-07T08:27:01ZMark FletcherMilestone Quick Action not displayed with no project milestones but with group milestones### Summary
Milestone Quick Action not displayed with no project milestones but with group milestones
### Steps to reproduce
- Create a new group, `GroupA`
- Add a group milestone, "Group Milestone"
- Create a new project in `GroupA`,...### Summary
Milestone Quick Action not displayed with no project milestones but with group milestones
### Steps to reproduce
- Create a new group, `GroupA`
- Add a group milestone, "Group Milestone"
- Create a new project in `GroupA`, `ProjectX`
- Do not create a project-level milestone
- Create a new issue in `ProjectX`
- Attempt to assign the new issue to the "Group Milestone" via quick action `/milestone`
- Notice that the quick action is not available
### Example Project
- https://gitlab.com/issue-reproduce/group-milestone-refs/issues/1
### What is the current *bug* behavior?
- `/milestone` Quick action is not available if group milestones but no project milestones available
### What is the expected *correct* behavior?
- `/milestone` Quick action should be available if group milestones or project milestones available
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
### Output of checks
~"reproduced on GitLab.com" v10.4.1
### Possible fixes🙈 jacopo beschi 🙉intrip@gmail.com🙈 jacopo beschi 🙉intrip@gmail.comhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/42336Deprecation message for dynamic milestone pages2019-09-10T19:50:22ZVictor Wuvictor@gitlab.comDeprecation message for dynamic milestone pages- Deprecation message/graphic for dynamic milestone pages to indicate that we will remove them in a future release.
- In the message/graphic, include some instructions on how to click to one of the project milestones and click `Promote` ...- Deprecation message/graphic for dynamic milestone pages to indicate that we will remove them in a future release.
- In the message/graphic, include some instructions on how to click to one of the project milestones and click `Promote` so that they can promote their project milestone into a group milestone.
- More context here: https://gitlab.com/gitlab-org/gitlab-ce/issues/39545.
- There are two dynamic milestone pages:
- Group level: E.g. https://gitlab.com/groups/gitlab-org/-/milestones/100?title=10.0
- Dashboard level: E.g. https://gitlab.com/dashboard/milestones/95?title=9.5
#### Design
##### Copy in the banner
```
This page will be removed in a future release.
Use group milestones to manage issues from multiple projects in the same milestone.
<a href="inline-dropdown">Promote these project milestones into a group milestone.</a>`
```
- The `Learn more` button link goes to a docs page explaining the whole context, including the warning of not having burndown charts for group milestones yet, and linking to the open issue for it. It also contains other limitations of group milestones and those open issues.
- Clicking `Promote these project milestones into a group milestone`, and then dropdown (popover) shows up.
##### Copy in the popover
```
1. Click any <b>project name</b> in the project list below to navigate to the project milestone.
2. Click the <b>Promote</b> button in the top right corner to promote it to a group milestone.
<a>Learn more</a>
```
- The `Learn more` link : [path-to-docs-ce-or-ee]/user/project/milestones/#promoting-project-milestones-to-group-milestones
- Icons: You can find them in `gitlab-svgs`.
| 01 | 02 - Popover |
| -- | ------------ |
| ![message](/uploads/a78e1a6fa4d0ece72e5b28299ac3c6db/message.png) | ![message--popover](/uploads/60234d73af19a2104097c0a53e560fae/message--popover.png) |
##### SVG
You can find `milestone_removing-page` in gitlab-svgs.10.8Luke BennettHazel YangLuke Bennetthttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/41895Modal and banner designs for project label and project milestone promotion2019-08-07T08:27:43ZJose Ivan VargasModal and banner designs for project label and project milestone promotionAs part of our current efforts to change all of the modals to the new design, the promote label/milestone design needs to be updated to be consistent
Curently we only have change the copy text from the issue https://gitlab.com/gitlab-or...As part of our current efforts to change all of the modals to the new design, the promote label/milestone design needs to be updated to be consistent
Curently we only have change the copy text from the issue https://gitlab.com/gitlab-org/gitlab-ce/issues/40920
Part of the efforts for: https://gitlab.com/gitlab-org/gitlab-ce/issues/28849
#### Designs
##### Promote a label/milestone to group level
- When promoting on project milestones list page, remain (refreshing if necessary) on project milestones list page, with the banner message.
- When promoting on the project milestone page, redirect to the group milestone page of the new group milestone. Use same banner message.
| | Labels | Milestones (EE) | Milestones (CE)
|-- | ------ | --------- | --------- |
| Modal design | ![promote-label](/uploads/84168446c6d77b5e8d943bb6659d5a91/promote-label.png) | ![promote-milestone-ee](/uploads/778f34cb1b6d57ecc143ff97c185c2fd/promote-milestone-ee.png) The link should go to https://docs.gitlab.com/ee/user/project/milestones/. These docs will indicate missing features. | ![promote-milestone-ce](/uploads/d74143f363eff2b48c99456187ce0fd4/promote-milestone-ce.png) |
| Modal title | Promote ~Discussion to group label?` | Promote 9.5 to group milestone? | Promote 9.5 to group milestone? |
| Modal body | Promoting [label] will make it available for all projects inside [Group name]. Existing project labels with the same name will be merged. This action cannot be reversed. | Promoting [milestone] will make it available for all projects inside [Group name]. Existing project milestones with the same name will be merged.[New Paragraph] Group milestones are <a href="docs-link">currently missing features such as burndown charts</a>. You will not have these features once you've promoted a project milestone. They will be available in future releases. [New Paragraph] This action cannot be reversed. | Promoting [milestone] will make it available for all projects inside [Group name]. Existing project milestones with the same name will be merged. This action cannot be reversed. |
##### Banners
- Can only promote on project lists page. When promoting, remain (refreshing if necessary) on project labels/milestones list page, with the banner message, which has a link to the group object.
| | Labels | Milestones |
| -- | ------ | --------- |
| Banner design | ![labels-project-banner-promote](/uploads/534048ad57ad125c346a71f6bc9899b0/labels-project-banner-promote.png) | ![milestone-project-promoted](/uploads/7415d843e2243ec3bd2a2a65fe9c7048/milestone-project-promoted.png) |
| Copy | Discussion promoted to <a>group label</a> | 9.1 promoted to <a>group milestone</a> |
cc @hazelyang10.6Hazel YangJose Ivan VargasHazel Yanghttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/41715Boards stay empty if filter it on a milestone that contains "+"2021-11-08T16:21:39ZKevinBBoards stay empty if filter it on a milestone that contains "+"**Step to reproduce:**
1. Create a milestone with a "+" in its name.
1. Associate few issue to this milestone.
1. Create a new board and add a milestone filter.
1. Select the freshed created milestone.
1. Board stays empty.
**To make i...**Step to reproduce:**
1. Create a milestone with a "+" in its name.
1. Associate few issue to this milestone.
1. Create a new board and add a milestone filter.
1. Select the freshed created milestone.
1. Board stays empty.
**To make it working:**
1. Rename the milestone and remove the sign "+"
1. Display the board again.
1. Board displays the issues.Backloghttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/41671Start/due dates on milestones decrease when editing2021-05-21T18:56:37ZJoel FeinerStart/due dates on milestones decrease when editing### Summary
If a milestone has a start and/or due date, when the milestone is edited, the dates are decreased by one or two days. This is apparent as soon as you open the editor. If you correct the dates before saving, they will remain ...### Summary
If a milestone has a start and/or due date, when the milestone is edited, the dates are decreased by one or two days. This is apparent as soon as you open the editor. If you correct the dates before saving, they will remain corrected. Thus, the problem appears to be when the editor is opened.
### Steps to reproduce
1. Create a milestone and assign a start date and a due date.
2. Edit the milestone. Observe that the dates have changed in the date pickers (this is not okay).
3. Save the milestone. The dates do not change from what's in the editor (this is okay).
### Example Project
https://gitlab.com/JoelFeiner/BugTest/milestones/1
The dates are Jan 4, 2018 and Jan 11, 2018. If you edit the milestone, you will see in the editor view that the dates are Jan 3, 2018 and Jan 10, 2018.
### What is the current *bug* behavior?
Dates decrement in some fashion when editing.
### What is the expected *correct* behavior?
Dates do not change unless explicitly changed.
### Relevant logs and/or screenshots
![image](/uploads/2fb0f9f31357da2a92ab705e058d01dd/image.png)
### Output of checks
This bug happens on GitLab.com.11.2https://gitlab.com/gitlab-org/gitlab-foss/-/issues/41476Enable Project Milestone Deletion via the API2019-08-07T08:28:06ZzhuzhiyangEnable Project Milestone Deletion via the API### Description
Enable Project Milestone Deletion via the API
### Proposal
Project milestone removal is available in the web interface. Let's support this in the API.
DELETE /api/v4/projects/:project_id/milestones/:milestone_id
### ...### Description
Enable Project Milestone Deletion via the API
### Proposal
Project milestone removal is available in the web interface. Let's support this in the API.
DELETE /api/v4/projects/:project_id/milestones/:milestone_id
### Links / references
🙈 jacopo beschi 🙉intrip@gmail.com🙈 jacopo beschi 🙉intrip@gmail.comhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/41314New design for project milestone deletion confirmation2018-03-05T10:58:51ZInactive AccountNew design for project milestone deletion confirmationPart of https://gitlab.com/gitlab-org/gitlab-ce/issues/28849
| Path | Current Screenshot | New Title | New Description | New Buttons |
|------|--------------------|-----------|-----------------|-------------|
| [`project/issues/mileston...Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/28849
| Path | Current Screenshot | New Title | New Description | New Buttons |
|------|--------------------|-----------|-----------------|-------------|
| [`project/issues/milestones`](http://localhost:3000/gitlab-org/gitlab-ce/milestones) | <img src="/uploads/b1c9b2669ee69620e537353ab336d78c/issue-milestone--delete.png" width=50% /> | **Delete milestone ‘[Milestone name]’?** | You’re about to permanently delete the milestone **[Milestone name]** from this project. This will remove **[Milestone name]** from [Issue count] issue[s] and [MR count] merge request[s]. Once deleted, it cannot be undone or recovered. | [Cancel] [Delete milestone] |
If there is no issues and merge requests:
```
You’re about to permanently delete the milestone [Milestone name] from this project.
[Milestone name] is not currently used in any issues or merge requests.
```10.5Hazel YangHazel Yanghttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/40920Emphasize irreversibility in warning message when promoting labels and milest...2019-08-07T08:28:41ZVictor Wuvictor@gitlab.comEmphasize irreversibility in warning message when promoting labels and milestones- We've had at least one report of a customer mistakenly promote milestones: https://gitlab.slack.com/archives/C0AR2KW4B/p1512661192000408.
- Let's update the warning message to be more explicit that you cannot reverse the action.
Curre...- We've had at least one report of a customer mistakenly promote milestones: https://gitlab.slack.com/archives/C0AR2KW4B/p1512661192000408.
- Let's update the warning message to be more explicit that you cannot reverse the action.
Current messages:
![Screen_Shot_2017-12-07_at_10.46.29](/uploads/50a9360a60c24be6eb1e6e4140858157/Screen_Shot_2017-12-07_at_10.46.29.png)
![Screen_Shot_2017-12-07_at_11.03.11](/uploads/ea23230488735f82b3ba1f136acbdacc/Screen_Shot_2017-12-07_at_11.03.11.png)
### Change to:
- Promoting this milestone will make it available for all projects inside the group. Existing project milestones with the same name will be merged. This action cannot be reversed. Are you sure?
- Promoting this label will make it available for all projects inside the group. Existing project label with the same name will be merged. This action cannot be reversed. Are you sure?
10.5Jose Ivan VargasJose Ivan Vargashttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/40916Viewing and filtering issues and merge requests in subgroups in lists and boards2021-11-08T16:21:58ZVictor Wuvictor@gitlab.comViewing and filtering issues and merge requests in subgroups in lists and boards### Background and current implementation
- Issues are scoped at the project level.
- Labels are scoped at the project level _and_ group level.
- Milestones are scoped at the project level _and_ group level.
- Currently, despite having s...### Background and current implementation
- Issues are scoped at the project level.
- Labels are scoped at the project level _and_ group level.
- Milestones are scoped at the project level _and_ group level.
- Currently, despite having subgrouping functionality, we do not support visibility of issues being rolled up beyond their immediate parent group.
### Proposed changes
| | Current | Proposed |
| --- | --- | --- |
| Assign label to issue/mr | Assign project label or group label, limited to only immediate parent group | Expand to all ancestor groups #40915 |
| Assign milestone to issue/mr | Assign project milestone or group milestone, limited to only immediate parent group | Expand to all ancestor groups #36862 |
| Project list views of issues/mrs | View objects in that project | No change |
| Project board of issues | View issues in that project | No change |
| Project list filtering of issues/mrs | Filter by labels/milestones of current project immediate parent group | Expand to labels/milestones of all ancestor groups |
| Project board filtering, saved config, and columns of issues/mrs | Filter by labels/milestones of current project and immediate parent group | Expand to labels/milestones of all ancestor groups |
| Group list views of issues/mrs | View objects of current group's immediate children projects | Expand to objects of all projects of all descendent groups #30106 |
| Group board view of issues | View issues of current group's immediate children projects | Expand to issues of all projects of all descendent groups https://gitlab.com/gitlab-org/gitlab-ee/issues/3342 |
| Group list filtering of issues/mrs by labels/milestones | Filter by labels/milestones of current group and immediate children projects | Expand to labels/milestones of all descendent groups and all descendent projects |
| Group board filtering, saved config, and columns of issues/mrs by labels/milestones | Filter by labels/milestones of current group | Expand to labels/milestones of all descendent groups and all descendent projects |https://gitlab.com/gitlab-org/gitlab-foss/-/issues/40602Promoting a project milestone to a group one had as a result to assign that m...2019-08-07T08:29:01ZAchilleas PipinellisPromoting a project milestone to a group one had as a result to assign that milestone to a bunch of issues/MRs.As the title says, promoting a project milestone to a group one had as a result to assign that milestone to a bunch of issues/MRs.
@MadLittleMods wrote ([chat link](https://gitlab.slack.com/archives/C0NFPSFA8/p1511808524000127)
) that r...As the title says, promoting a project milestone to a group one had as a result to assign that milestone to a bunch of issues/MRs.
@MadLittleMods wrote ([chat link](https://gitlab.slack.com/archives/C0NFPSFA8/p1511808524000127)
) that recently he promoted the 10.4 milestone from https://gitlab.com/gitlab-com/customers-gitlab-com/milestones/7 to a group milestone https://gitlab.com/groups/gitlab-com/-/milestones/6.
I think it's related, and that caused **a lot** of issues/MRs under the `gitlab-com` namespace to get assigned to this milestone. Strangely enough, there's no system note in any of those, it just happened behind the scenes.
## Useful links
- 4 years ago MRs with a recent 10.4 milestone: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests?milestone_title=10.4&page=373&scope=all&state=all, that can't be right
- Issue opened by a guest user, got the 10.4 milestone added to it although non-members do not have access to do this: https://gitlab.com/gitlab-com/gitlab-docs/issues/143 (you can see in the system note I removed it)
## Steps to reproduce
I'm not really sure, we've promoted other milestones in the past, but maybe a conflict of their iids caused this? I'm not really sure.
cc @victorwu @smcgivern10.2https://gitlab.com/gitlab-org/gitlab-foss/-/issues/40338New group milestone breadcrumb is broken2019-08-07T08:29:22ZPedro Moreira da SilvaNew group milestone breadcrumb is broken### Summary
The breadcrumb when creating a new group milestone is broken (see screenshot below).
### Steps to reproduce
Visit the “New milestone” screen in a group
### What is the current *bug* behavior?
The breadcrumb shows the “Mi...### Summary
The breadcrumb when creating a new group milestone is broken (see screenshot below).
### Steps to reproduce
Visit the “New milestone” screen in a group
### What is the current *bug* behavior?
The breadcrumb shows the “Milestone” link duplicated and wrongly formatted
![image](/uploads/5ff73a4777a2e03d851ea3e08d7c2386/image.png)
### What is the expected *correct* behavior?
![image](/uploads/8811357211eda4ed41d4861fcb6f4e97/image.png)
### Output of checks
This bug happens on GitLab.comPhil HughesPhil Hugheshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/40178Add milestone indicator to issue board cards2021-11-08T16:22:22ZDimitrie HoekstraAdd milestone indicator to issue board cards### Problem
Currently when there is no milestone selected as a filter, there is no way of knowing which milestone that issue has or hasn't, unless you select it and open the sidebar.
![image](https://gitlab.com/gitlab-org/gitlab-ee/upl...### Problem
Currently when there is no milestone selected as a filter, there is no way of knowing which milestone that issue has or hasn't, unless you select it and open the sidebar.
![image](https://gitlab.com/gitlab-org/gitlab-ee/uploads/dfc922a68e7b032008651627d7ddb81e/image.png)
### Proposal
With the introduction of https://gitlab.com/gitlab-org/gitlab-ee/issues/4006 there will be a weight indicator, let's have that for milestones as well.
![img](https://gitlab.com/gitlab-org/gitlab-ee/uploads/c3366035fe44b1f1614e19fd106cad10/image.png)Backloghttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/39995Remove fake milestones on group milestones page, and/or redesign to show proj...2019-08-07T08:29:56ZVictor Wuvictor@gitlab.comRemove fake milestones on group milestones page, and/or redesign to show project milestones- On the group milestones list page of a group, it is currently displaying fake or "dynamic" milestones, which are just project milestones grouped together in the same name.
- This should be redesigned, possibly by removing them.
- Howev...- On the group milestones list page of a group, it is currently displaying fake or "dynamic" milestones, which are just project milestones grouped together in the same name.
- This should be redesigned, possibly by removing them.
- However, there are still benefits of accessing (or at least navigating indirectly to) project milestones from this page. We need a new design to address this.https://gitlab.com/gitlab-org/gitlab-foss/-/issues/39850Markdown refs to closed milestones are not converted to link2019-08-07T08:30:04ZJoel FeinerMarkdown refs to closed milestones are not converted to link### Summary
Using markdown links to milestones (e.g. "%1") does not generate a link to the milestone if it is closed.
### Steps to reproduce
1. Create milestone.
2. Close milestone.
3. In an issue, wiki page or somewhere else that sup...### Summary
Using markdown links to milestones (e.g. "%1") does not generate a link to the milestone if it is closed.
### Steps to reproduce
1. Create milestone.
2. Close milestone.
3. In an issue, wiki page or somewhere else that supports markdown, using the milestone reference syntax (e.g. "%1") to create a link. It will not be replaced with an actual link.
### What is the current *bug* behavior?
Markdown ref comes through as plain text.
### What is the expected *correct* behavior?
Markdown ref is converted to hyperlink to milestone.
### Relevant logs and/or screenshots
None.
#### Results of GitLab environment info
```
System information
System:
Current User: git
Using RVM: no
Ruby Version: 2.3.5p376
Gem Version: 2.6.13
Bundler Version:1.13.7
Rake Version: 12.1.0
Redis Version: 3.2.5
Git Version: 2.13.5
Sidekiq Version:5.0.4
Go Version: unknown
GitLab information
Version: 10.1.0
Revision: 5a695c4
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://<REDACTED>
HTTP Clone URL: https://<REDACTED>/some-group/some-project.git
SSH Clone URL: git@<REDACTED>:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 5.9.3
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
```
#### Results of GitLab application Check
```
Checking GitLab Shell ...
GitLab Shell version >= 5.9.3 ? ... OK (5.9.3)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
19/99 ... ok
20/101 ... ok
20/102 ... ok
20/103 ... ok
20/104 ... ok
20/105 ... ok
21/106 ... ok
21/108 ... ok
21/109 ... ok
21/110 ... ok
21/112 ... ok
21/114 ... ok
21/115 ... ok
21/117 ... ok
19/118 ... ok
21/119 ... ok
21/120 ... ok
21/121 ... ok
7/122 ... ok
21/123 ... ok
21/124 ... repository is empty
21/127 ... repository is empty
21/128 ... ok
21/129 ... repository is empty
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
IMAP server credentials are correct? ... yes
Init.d configured correctly? ... skipped
MailRoom running? ... skipped
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
19/99 ... yes
20/101 ... yes
20/102 ... yes
20/103 ... yes
20/104 ... yes
20/105 ... yes
21/106 ... yes
21/108 ... yes
21/109 ... yes
21/110 ... yes
21/112 ... yes
21/114 ... yes
21/115 ... yes
21/117 ... yes
19/118 ... yes
21/119 ... yes
21/120 ... yes
21/121 ... yes
7/122 ... yes
21/123 ... yes
21/124 ... yes
21/127 ... yes
21/128 ... yes
21/129 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.5)
Git user has default SSH configuration? ... yes
Active users: ... 8
Checking GitLab ... Finished
```
### Possible fixes
Unknown.blackst0neblackst0ne.ru@gmail.comblackst0neblackst0ne.ru@gmail.comhttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/39848New Group Milestone shows empty dashboard2021-11-08T16:22:27ZMichael BisbjergNew Group Milestone shows empty dashboard### Summary
We've previously created project milestones, and "promoted" them to Group Milestones (iirc). Just now, however, I created a Group Milestone "first", but am unable to see anything in it. I can attach project-level issues an M...### Summary
We've previously created project milestones, and "promoted" them to Group Milestones (iirc). Just now, however, I created a Group Milestone "first", but am unable to see anything in it. I can attach project-level issues an MR's just fine (and see the numbers in the group dashboard), but not the projects or anything like other group dashboards.
### Steps to reproduce
* Create Group milestone
* In group project, attach issue / MR's to new group milestone
* Observe empty group milestone dashboard
### Example Project
I have reproduced on Gitlab.com, in the following public Group / Project:
* https://gitlab.com/groups/MiketestGroup01/milestones/1
### What is the current *bug* behavior?
The group milestone dashboard is empty. Observe the counts on the right side are correct (also on our local instance) - they show the correct number of issues etc.
This only happens on new Group Milestones. New Project Milestones behave as expected.
![image](/uploads/8a7a2a430da2b32a1de556ff8629f131/image.png)
### What is the expected *correct* behavior?
This is a screenshot from an older Milestone we had. A newly created milestone on our Gitlab-CE 10.1.0 installation exhibits the same behaviour as seen on Gitlab.com.
I expected to see the individual projects, and an issue dashboard.
![image](/uploads/a3fd201012e8197e6e7834fd2217e51d/image.png)
### Relevant logs and/or screenshots
Seen above.
### Output of checks
N/A
#### Results of GitLab environment info
N/A
#### Results of GitLab application Check
N/A
### Possible fixes
N/Ahttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/39720Group Milestone Sorting2019-08-07T08:30:13ZMarkus ThurnerGroup Milestone Sorting### Description
Milestones can be sorted by various dates on a project level.
However, we're managing our team's backlog across multiple projects. We end up looking at the milestone overview on the group level. This view misses the dro...### Description
Milestones can be sorted by various dates on a project level.
However, we're managing our team's backlog across multiple projects. We end up looking at the milestone overview on the group level. This view misses the drop down to sort by date.
### Proposal
Add sort by date option to milestones on the group-level view.
#### Use cases
We use GitLab by teams creating groups. So a group matches a team. Each team has several projects.
Teams tend to look at their work (in progress, planning) on the group level. Allowing milestones to sort by start date on the group level would be a first start to support planning. (Long term, I wish that I can put milestones in a Kanban board to prioritize them.)10.3George AndrinopoulosGeorge Andrinopouloshttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/39544Dashboard milestone list page redesign2019-08-07T08:30:29ZVictor Wuvictor@gitlab.comDashboard milestone list page redesignDesign from https://gitlab.com/gitlab-org/gitlab-ce/issues/35833.
#### Dashboard milestone
- e.g. https://gitlab.com/dashboard/milestones
- This is currently only showing project milestones and not showing any date information. Add th...Design from https://gitlab.com/gitlab-org/gitlab-ce/issues/35833.
#### Dashboard milestone
- e.g. https://gitlab.com/dashboard/milestones
- This is currently only showing project milestones and not showing any date information. Add the date information. Use a design similar to https://gitlab.com/gitlab-org/gitlab-ce/issues/39542.
- Implement the new visual design.
![milestone-dashboard](https://gitlab.com/gitlab-org/gitlab-ce/uploads/c4dbaee7645751b8d6c1dbb795883fae/milestone-dashboard.png)https://gitlab.com/gitlab-org/gitlab-foss/-/issues/39543Milestone page list redesign2019-09-10T23:37:19ZVictor Wuvictor@gitlab.comMilestone page list redesignDesign from https://gitlab.com/gitlab-org/gitlab-ce/issues/35833
#### Project milestone list page
- For project milestones in this page, there are links to the actual project milestone for that project.
- For group milestones, date inf...Design from https://gitlab.com/gitlab-org/gitlab-ce/issues/35833
#### Project milestone list page
- For project milestones in this page, there are links to the actual project milestone for that project.
- For group milestones, date information is currently _not_ being shown. Date information should be added. Use a design similar to https://gitlab.com/gitlab-org/gitlab-ce/issues/39542.
![milestone-project](/uploads/6326d98b54ccebb1ecb13e113cf59ac2/milestone-project.png)
#### Group milestone list page
- e.g. https://gitlab.com/groups/gitlab-org/milestones
- Some of the milestones are group milestones. Others are project milestones. So display that accordingly.
- The milestones in "Closed" tab have a "Closed" label in the background-color `$red-500 :: DB3B21`
| Open | Close |
|------|-------|
| ![milestone-group](/uploads/f9c662cd127aca2f23f82ee354366b55/milestone-group.png) | ![milestone-group-closed](/uploads/13e48a703eb7241881790e792b245ca7/milestone-group-closed.png) |
#### Dashboard milestone list page
- e.g. https://gitlab.com/dashboard/milestones
- This is currently only showing project milestones and not showing any date information. Add the date information. Use a design similar to https://gitlab.com/gitlab-org/gitlab-ce/issues/39542.
- Implement the new visual design.
![milestone-dashboard](/uploads/5ca638204ec3ffb36b0adf3683befe4b/milestone-dashboard.png)
#### Status of milestone
- The milestone has the different badges depends on the status.
* Upcoming
* Closed
* Expired
| Upcoming | Closed | Expired |
| -------- | ------- | ------- |
| ![milestone-project--upcoming](/uploads/7e1ba47db862931280f21cdb43fe791f/milestone-project--upcoming.png) | ![milestone-project--closed](/uploads/4e99a307f754c311bb18814ada740b9c/milestone-project--closed.png) | ![milestone-project--expired](/uploads/9085c1b54337aeebffefc27c77cb6670/milestone-project--expired.png)|
| Background color: `$blue-500 :: 1F78D1`| Background color: `$red-500 :: DB3B21`| Background color: `$orange-500 :: FC9403`|
11.1Hazel YangConstance OkoghenunHazel Yanghttps://gitlab.com/gitlab-org/gitlab-foss/-/issues/39542Project milestone list page redesign2019-08-07T08:30:30ZVictor Wuvictor@gitlab.comProject milestone list page redesignDesigns from https://gitlab.com/gitlab-org/gitlab-ce/issues/35833
#### Project milestone list page
- e.g. https://gitlab.com/gitlab-org/gitlab-ce/milestones
- All the milestones here are project milestones, so display that accordingly...Designs from https://gitlab.com/gitlab-org/gitlab-ce/issues/35833
#### Project milestone list page
- e.g. https://gitlab.com/gitlab-org/gitlab-ce/milestones
- All the milestones here are project milestones, so display that accordingly.
- If no dates entered, display nothing.
- If start date entered only, display `Start date: Aug 17, 2017`
- If end date entered only, display `End date: Aug 18, 2017`
- If both start date and end date entered, display `Aug 17, 2017 - Aug 18, 2017`
- If the end date is entered _and_ today is after the end date _and_ the milestone is open, it is a past due milestone.
| Open | Closed |
|------|--------|
| ![milestone-project](https://gitlab.com/gitlab-org/gitlab-ce/uploads/990c6be784a9c3ffca76e69cedc611e9/milestone-project.png)![milestone-project](https://gitlab.com/gitlab-org/gitlab-ce/uploads/fbeb735dd839c7f184e06f85cdc19413/milestone-project.png) | ![milestone-project-closed](https://gitlab.com/gitlab-org/gitlab-ce/uploads/8d7fbaab70bc3caf92df156798e64f81/milestone-project-closed.png) |