Bulk edit issues to assign/unassign an Epic (#210470) · Issues · GitLab.org / GitLab

Bulk edit issues to assign/unassign an Epic

Problem to solve

As a user of the Issue List, I'd like to edit the Epic value of multiple issues at a time, so I can bulk > assign/unassign issues to epics

Intended users

Further details

Now that we allow users to filter by an epic (#195704 (closed)), we should enable a bulk edit feature as well.

Add the ability to bulk edit epics on both Project and Group issues pages.

Proposal

Add an Epic dropdown field in the Bulk Edit sidebar that allows users to assign an Epic or unassign multiple issues from an epic:

Permissions and Security

Same as current bulk editing permissions

Documentation

Update existing Bulk edit docs

Availability & Testing

Links / references

/label feature

### Problem to solve

> As a user of the Issue List, I'd like to edit the Epic value of multiple issues at a time, so I can bulk > assign/unassign issues to epics

### Intended users

* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)

### Further details

Now that we allow users to filter by an epic (https://gitlab.com/gitlab-org/gitlab/-/issues/195704), we should enable a bulk edit feature as well.

Add the ability to bulk edit epics on both Project and Group issues pages.

### Proposal

Add an Epic dropdown field in the Bulk Edit sidebar that allows users to assign an Epic or unassign multiple issues from an epic:
![Epic_bulk_option](/uploads/acb3470027c3c99dc7fb3482712363db/Epic_bulk_option.png)

### Permissions and Security

Same as current bulk editing permissions

### Documentation

Update existing [Bulk edit](https://docs.gitlab.com/ee/user/project/bulk_editing.html) docs

### Availability & Testing

<!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.

What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change

See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning -->

### Links / references

/label ~feature

Edited May 05, 2020 by Donald Cook

Discussion
Designs