Issues for KDE migration to Gitlab

See gitlab-org/gitlab#24900 (moved) for the preface, this issue is the meant as tracker to list the issues affecting KDE. I will update the list with issues we're getting affected.

Critical

• Support for multiple project boards : gitlab-org/gitlab-foss#53811 (closed) - went out in GitLab 12.1
• Ability to invite users to a confidential issue: gitlab-org/gitlab#20660 and gitlab-org/gitlab#20252 - This blocks the migration of tasks, not code. Status: Both of these are accepting merge requests from the community.

Important

• Port Merge Request Reviews from GitLab EE to GitLab CE : gitlab-org/gitlab#28154 (closed) - Status: Merged, released in GitLab 13.1
• Optional merge request approvals for GitLab CE: gitlab-org/gitlab#27426 (closed) -- Status: Merged, released in GitLab 13.2"
• Optional merge request approvals do not send notifications: gitlab-org/gitlab#231351 (closed)

Nice to have

• Add project configuration option to require MRs to have the allow_collaboration flag set gitlab-org/gitlab#25889 - KDE will probably provision a bot to handle that as an interim workaround.
• Blocker/sub-task/parent task tracking support for Issues : gitlab-org/gitlab#29914: Related issue covers the most of requirement.
• Move blocker issue feature to CE : gitlab-org/gitlab#273596
• You can only rewrite the final commit message in the web UI for squashable merge requests gitlab-org/gitlab#219747 (closed)
• When force-pushing to update a merge request, context for changes is lost gitlab-org/gitlab#241509
• Group Level Description Templates for Issues, Epics, and Merge Requests (Seems already WIP) gitlab-org/gitlab#7749 (closed)

Various bugs

• Optional merge request approvals show up wrongly in activity feed: gitlab-org/gitlab#231306 (closed)
• Merge request info is lost when merging squashed commits with fast-forward policy gitlab-org/gitlab#208344
• Large images in merge requests are always displayed at full size and take up a lot of space gitlab-org/gitlab#249235 (closed)
• User autocomplete not working for members of groups invited to groups gitlab-org/gitlab#209101 (closed)

changed the description

/cc @dplanella

changed the description

One of most requested feature from community during the evaluation process is availability of batch review, and I am rather confused by the https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22158

As far as I understand, this feature is backported to the community edition? or not? Can someone clarify this to me?

this feature is backported to the community edition? or not? Can someone clarify this to me?

The merge request referenced (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22158) only backports any CE changes that we made in EE. It doesn't backport the feature, only some Vue component and JS changes to make conflicts between CE & EE happen less often.

Thanks for explaining.

@dplanella With regards to gitlab-ce#42096 is there anything needed on our side to progress that given the popularity of the issue?

Based on request and feedback from community I am going to move merge request approvals to the blocker issues.

changed the description

Hello, Is there any chance feature implemented in gitlab-org/gitlab-ee#1984 moved to gitlab-ce? It is one of most requested feature that people want and are annoyed due to lack of it, specially in larger code review.

Based on @jramsay comment on kde-core-devel, related issues : gitlab-ce#40557 and gitlab-ce#60690

mentioned in epic gitlab-org&1406 (closed)

mentioned in epic gitlab-org&1417

@bshah moving the entire approvals feature from gitlab-ce~2933322 to Core (https://gitlab.com/gitlab-org/gitlab-ce/issues/42096 ) isn't something we've been eager to do historically. There is an alternative simplified version that would add a basic optional approvals to merge requests https://gitlab.com/gitlab-org/gitlab-ce/issues/59197 - would that meet your needs?

Ah, optional approvals was discussed already, and we agreed that optional merge request approvals are fine for our use-case. (@bcooksley commented on one of issues, but I can't find out issue at moment).