Move all issues on closed milestone to the current development milestone
Basically automate gitlab-com/www-gitlab-com#3555 (closed)
So for example, we're starting %11.8 development and we move all issues at %11.6 to %11.8
Here's the current complete plan:
-
We move issues/MRs with %11.6 to %11.8 locally (ignore security): !87 (closed) The merge request is here for review and dry-run, but I'll run it locally because it's a one off script - This will generate two summary issues for issues and merge requests, for each projects we run against. (For now CE/EE/QA)
- CE issues: https://gitlab.com/gitlab-org/gitlab-ce/issues/56525
- CE merge requests: https://gitlab.com/gitlab-org/gitlab-ce/issues/56526
- EE issues: https://gitlab.com/gitlab-org/gitlab-ee/issues/9278
- EE merge requests: https://gitlab.com/gitlab-org/gitlab-ee/issues/9279
-
Then we move issues/MRs with any milestones which were closed to %Backlog locally (ignore security): !88 (closed) Again the merge request here is only for review and dry-run, and I'll run it locally. Since we already move %11.6 in the above step, this should only move %11.5 and below to %Backlog - This will generate another two summary issues for issues and merge requests, for each projects we run against. (For now CE/EE/QA)
- QA issues: gitlab-org/gitlab-qa#365 (closed)
- CE issues: https://gitlab.com/gitlab-org/gitlab-ce/issues/56528
- CE merge requests: https://gitlab.com/gitlab-org/gitlab-ce/issues/56530
- EE issues: https://gitlab.com/gitlab-org/gitlab-ee/issues/9280
- EE merge requests: https://gitlab.com/gitlab-org/gitlab-ee/issues/9281
-
Lastly, we should end up with issues/MRs with %11.7+, and we shouldn't have anything which is on a closed milestone. Then we can go and merge !83 (merged) and this will automate that: - It moves any issues/MRs on a closed milestone to the current development milestone, in a daily basis
- The current development milestone is defined as the active milestone which has the most recent starting date. Currently it's %11.8
develop_milestone = all_active_with_start_date.reverse_each .find { |m| m.start_date < today }
- This means as long as we close a particular milestone, next time it runs it'll move all the issues/MRs on that milestone to the current development milestone. It doesn't care if it's
+1
or+2
, it just moves everything to the current one. - Again for each runs it'll generate two summary issues for each projects we run against.
And we can think about security after we have some sense about how this works like.
Edited by Mek Stittri