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.
Gabe Weaverchanged 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 title from Bulk edit active timeboxes on issues/MRs within groups and projects to Bulk edit iterations on issues/MRs within groups and projects
Gabe Weaverchanged the descriptionCompare with previous version
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. :/
@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.
Mario de la Ossachanged title from Bulk edit iterations on issues/MRs within groups and projects to Bulk edit iterations on issues within groups and projects
changed title from Bulk edit iterations on issues/MRs within groups and projects to Bulk edit iterations on issues within groups and projects
Mario de la Ossachanged the descriptionCompare with previous version
@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?
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.
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.
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?
Hi, we are a GitLab Starter user. Thank you all for your work. GitLab is a great tool and works very well for us in some areas. We really would like to use it more for planning as well in the future.
The iterations feature is very important to us as it finally helps us to better plan our work. Especially the functionality described in this issus is important, as it is the only thing missing that keeps us from using iterations instead of milestones for our sprints.
Let me explain our workflow:
in sprint planning our issues are assigned to a sprint milestone (hopefully iteration in the future)
developers are working on the issues during the sprint
in sprint review some of the remaining issues are moved from one sprint milestone to another (hopefully iteration in the future)
So using iterations instead of milestones in step 3 above we would need to:
go to the issue list and filter for an iteration
bulk edit the issues and assign the new iteration
Doing step 3 manually for every issue is dumb work, which we do not have time for. If this is not available in GitLab Starter we would need to keep on using milestones to mark our sprints, which keeps us from using milestones for what they were designed for: to track versions/releases.
We have been waiting for iterations since we started using GitLab. Then we waited the last year for iterations to become really usable. And now we find out that it will not be in GitLab Starter? Imagine our frustration right now.
Is there no chance that this could make it for GitLab Starter?
I have not just been waiting for iterations, I have been closely following each and every issue on iteration and collaborate with everybody on the topic wherever possible to help shape it as my contribution to community. I was under the impression throughout the past year that this was a starter feature.
On the other hand, there is the blogpost from 26th that announced the changing tiers of subscription. Was this change in tier for this issue due to that subscription change? If so, I believe we still have an year to convert to Premium, right? Does this mean that while we'll continue to pay for starter, nothing new will added to that tier?
I should probably discuss this elsewhere! Please advise.
@k.rahul thanks for pointing this out, didn't know about the killing of GitLab Starter on the time of my post. hmmm. unsure what we will do when our license expires.
@common_knowledge yes, but you can bulk edit issues on single repos as well, which is what we do. we are currently collecting all issues in one repo and are using the iterations of the group (iterations can only be created at group level).
@gweaver thank you for changing it back to GitLab Starter, we really look forward to this.
@s.mittelberger.pexta@k.rahul thanks for raising your use cases and questions. I was still in the midst of figuring out how to move forward with existing Starter features when I updated (now reverted) the tier label on this issue. I can't speak for all the other product groups at GitLab, but for Plan, we're going to continue tiering Iterations and other Starter focused features in Starter. We're no longer selling Starter to new customers, but Starter will technically still exist for current customers for a few years as far as I understand things. As soon as there are no more customers on Starter, we'll move things to Premium.
In terms of bulk updating Iterations, doing so from the List view will work. You'll also be able to leverage Boards as soon as this ships (#250479 (closed)).