Bulk edit iterations on issues within groups and projects

Problem to solve

Given there are now iterations, issue lists should support bulk editing iterations.

Proposal

1. You should be able to bulk edit Iteration

Context

This is a follow on from the initial MVC for adding iterations - https://gitlab.com/gitlab-org/gitlab/issues/35290e

Release notes

Instead of having to manually update the iteration on issues one at a time, iterations can now be bulk updated from the issue list of a group or project.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

added Category:Issue Tracking devopsplan groupproject management typefeature workflowplanning breakdown labels

added to epic &2422

mentioned in issue #197801 (closed)

mentioned in issue #198984 (closed)

mentioned in issue #201640 (closed)

added docsfeature documentation labels

changed title from Bulk edit active timeboxes on issues/MRs within groups and projects to Bulk edit iterations on issues/MRs within groups and projects

changed the description

mentioned in epic &2422

added sectiondev label

Extremely interested in this.

/cc @SteveTerhar

Customer SF link for tracking purposes (internal only) https://gitlab.my.salesforce.com/0014M00001nISiT

added customer label

mentioned in issue #257772 (closed)

We are a silver customer and also interested on this.

mentioned in issue #261979 (closed)

mentioned in issue #20434 (closed)

mentioned in issue gitlab-org/quality/triage-reports#473 (closed)

mentioned in issue gitlab-org/quality/triage-reports#533 (closed)

changed milestone to %13.7

Had a chat with a Silver prospect today (https://gitlab.my.salesforce.com/0064M00000YMR5A, internal link) They have concluded their evaluation of Iterations and expressed the need to add Iterations to Bulk Edit as critical for the Iterations maturity

@dzalbo FYI, we are a silver customer and iterations are mostly useless without the bulk edit feature. We manage multiple projects (for multiple customers) on a per sprint capacity basis, we currently are using "milestones" per each iteration wich is a bad usage of it but the only solution we had found. With this we lost the ability to track milestones. :/

added backend frontend labels

changed milestone to %13.8

added direction label

I'd say a 2 weight on the frontend, so let's use whatever weight backend comes up with.

@mdelaossa I know we talked briefly about this on Monday, but I forgot to ask about a weight. My guess would be a 3. Adding that for now, but feel free to adjust if you think differently.

I agree with 3. Most of this can borrow heavily from how we deal with Milestones, so the work is really fitting those patterns for Iterations

set weight to 3

@sstern As discussed, assigning this to you for iteration 14.

added workflowready for development label and removed workflowplanning breakdown label

assigned to @sstern

added release post item label

mentioned in issue gitlab-org/quality/triage-reports#1212 (closed)

assigned to @mdelaossa

@mdelaossa Moving this to workflowin dev

added Deliverable label

changed title from Bulk edit iterations on issues/MRs within groups and projects to Bulk edit iterations on issues within groups and projects

changed the description

reminder that MRs cannot be assigned to iterations, so I changed the title

added workflowin review label and removed workflowready for development label

mentioned in merge request !50113 (merged)

whoops, I shouldn't have put this in workflowin review yet since only the backend is in that state, sorry.

added workflowin dev label and removed workflowin review label

added GitLab Starter label

added quad-planningcomplete-no-action label

@gweaver @hollyreynolds so well be able to bulk update iterations. I have lots of questions but the main one right now being in the project/group issues list are we going to show the user there is an iteration assigned to an issue?

@sstern I believe we should. @hollyreynolds can you provide guidance here? Maybe slot it next to the milestone?

Ok sounds good, ill wait for @hollyreynolds response. But Im going to create an epic with what needs to be done with the sidebars. As it seems right now on this iteration, we wont be able to use the graphql mutation to update iterations because the whole payload is being sent back in a form. Well need to do a swap together.

The reason this is is because it could potentially complicate the user experience, what if iterations fails but the rest of the update succeeds etc.

@sstern do you think this will make it for 13.8? Just deciding if I need to do a release post MR before i take off for a few days of PTO.

Ya i have confidence, it'll behave like the other fields in the sidebar, but I was thinking about parsing out project and group MR's into two separate MR's.

Id say do a release post MR just in case and assign it to me and ill take it over when youre off.

WDYT?

Hey @sstern - just following up here as the RP prep is a bit compressed due to F&F day tomorrow. I saw that @mdelaossa's MR for bulk remove support (!51179 (merged)) was merged, which I know was blocking this, but I wanted to check on your confidence if the frontend for this is going to make it in for %13.8?

Update: In maintainer review. Sorry about the delay

mentioned in merge request !51179 (merged)