Show copy action in milestone list
What does this MR do and why?
Always show copy action in milestones for consistency, as this action is not permission dependent. This also ensures the group milestone list is consistently aligned as other actions depend on variable permissions, while this means an action is always present.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After | |
|---|---|---|
|
|
|
Milestones list |
|
|
|
Milestone detail, no permissions |
|
|
Milestone detail, with permissions (not changed) |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Open a group milestone list
- Verify the "Copy" action appears in the action menu
- Open a milestone and verify actions are correct based on permissions
To verify all states, invite a user to a project within a public group. The user should not be a member of the group, and should be a reporter+ in the project. Both the group and project must have 1+ milestone. Now open the group milestone list as that user — milestones from that project should have all edit actions available, while group milestones have only the copy action.
Related to #487230 (closed)