Enable group_iterations feature flag by default

doc/user/group/iterations/index.md

@@ -8,11 +8,12 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 # Iterations **(STARTER)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214713) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.1.
-> - It's deployed behind a feature flag, disabled by default.
-> - It's disabled on GitLab.com.
-> - It's able to be enabled or disabled per-group
-> - It's not recommended for production use.
-> - To use it in GitLab self-managed instances, ask a GitLab administrator to [enable it](#enable-iterations-core-only). **(CORE ONLY)**
+> - It was deployed behind a feature flag, disabled by default.
+> - [Became enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/221047) on GitLab 13.2.
+> - It's enabled on GitLab.com.
+> - It's able to be enabled or disabled per-group.
+> - It's recommended for production use.
+> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#disable-iterations-core-only). **(CORE ONLY)**
 
 Iterations are a way to track issues over a period of time. This allows teams
 to track velocity and volatility metrics. Iterations can be used with [milestones](../../project/milestones/index.md)
@@ -56,12 +57,11 @@ You need Developer [permissions](../../permissions.md) or higher to edit an iter
 
 To edit an iteration, click the three-dot menu (**{ellipsis_v}**) > **Edit iteration**.
 
-## Enable Iterations **(CORE ONLY)**
+## Disable Iterations **(CORE ONLY)**
 
-GitLab Iterations feature is under development and not ready for production use.
-It is deployed behind a feature flag that is **disabled by default**.
+GitLab Iterations feature is deployed with a feature flag that is **enabled by default**.
 [GitLab administrators with access to the GitLab Rails console](../../../administration/feature_flags.md)
-can enable it for your instance. `:group_iterations` can be enabled or disabled per-group.
+can disable it for your instance. `:group_iterations` can be enabled or disabled per-group.
 
 To enable it:
 

ee/app/helpers/ee/groups_helper.rb

@@ -150,7 +150,7 @@ module EE
         links << :productivity_analytics
       end
 
-      if ::Feature.enabled?(:group_iterations, @group) && @group.feature_available?(:iterations) && can?(current_user, :read_iteration, @group)
+      if ::Feature.enabled?(:group_iterations, @group, default_enabled: true) && @group.feature_available?(:iterations) && can?(current_user, :read_iteration, @group)
         links << :iterations
       end
 

ee/app/views/groups/iterations/index.html.haml

 - page_title _("Iterations")
 
-- if Feature.enabled?(:group_iterations, @group)
+- if Feature.enabled?(:group_iterations, @group, default_enabled: true)
   .js-iterations-list{ data: { group_full_path: @group.full_path, can_admin: can?(current_user, :create_iteration, @group).to_s, new_iteration_path: new_group_iteration_path(@group) } }

ee/app/views/groups/iterations/show.html.haml

@@ -2,5 +2,5 @@
 - breadcrumb_title params[:id]
 - page_title _("Iterations")
 
-- if Feature.enabled?(:group_iterations, @group)
+- if Feature.enabled?(:group_iterations, @group, default_enabled: true)
   .js-iteration{ data: { group_path: @group.full_path, iteration_iid: params[:id], can_edit: can?(current_user, :admin_iteration, @group).to_s, preview_markdown_path: preview_markdown_path(@group) } }

ee/app/views/shared/issuable/_iteration_select.html.haml

-- if Feature.enabled?(:group_iterations, @project.group) && @project.group.feature_available?(:iterations) && issuable_type == "issue"
+- if Feature.enabled?(:group_iterations, @project.group, default_enabled: true) && @project.group.feature_available?(:iterations) && issuable_type == "issue"
   .js-iteration-select{ data: { can_edit: can_edit, group_path: group_path, project_path: project_path, issue_iid: issue_iid } }

ee/changelogs/unreleased/jl-enable-iterations-by-default.yml

+---
+title: Enables Iterations by default
+merge_request: 36873
+author:
+type: added