Changelog: other

Hides over storage limit alerts for projects under limits
and for the group, except if in the group Usage Quotas.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150017
EE: true

Prior to this change, the `purchase_code_suggestions` feature flag was
enabled with the GA of Duo Pro back in February. Since then the feature
flag has been deemed stable.

This change removes the `purchase_code_suggestions` feature flag without
default enabling it given it only applies to GitLab.com.

Changelog: changed
EE: true

This reverts merge request !150052

Changelog: changed
EE: true

This MR implements handling for errors in the
frontend when the Zuora iframe should fail to load
and when general errors are thrown.

Changelog: changed
EE: true

This commit removes the huge ee/spec/models/factories_spec.rb in favor
of linting factories per associated model.

Linting is run in a isolated, outer context starting with `Lint
factories for <described_class>`.

This MR implements handling for errors in the
frontend and uses that to handle the
authentication required error from Stripe that
is a result of the 3DS authentication failing.

Changelog: changed
EE: true

Changelog: fixed

Changelog: added
EE: true

Add support for setting color and health status when creating a work item

Changelog: added

When the usage overview chart is rendered, we should display
an error message if the VSD background aggregation is not
yet enabled.

Now that `GlKeysetPagination`'s labels are properly externalized in
GitLab UI, we can set them once in the config.
This also unifies the labels we use: `prevText` will always be
`Previous` instead of `Prev` in some cases.

This MR removes the feature and documentation
for visual review tools.

Changelog: removed

- since we decided not to migrate users still in onboarding
  when we switch over to db only solution in
  https://gitlab.com/gitlab-org/gitlab/-/issues/435745#note_1839940950,
  we need to document via tests what to expect in those situations
  the best we can. This is the final test to cover that
  from the request layer.

When we are importing epics, either through file or direct import, we want to
create a synced work item along the epic.

This is also a preparation to keep the import functionality working as we
prepare to introduce the NOT NULL constraint on epics.issue_id column.

re https://gitlab.com/gitlab-org/gitlab/-/issues/446155

The XRay Add-On feature is now accessible to all subgroups and projects within the hierarchy of the namespace where the Add-On is purchased

Changelog: fixed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150065
EE: true

When the quantity of AddOnPurchase decreases during renewal,
we want to automatically remove the seat overage.

EE: true
Changelog: added

Migrates occurrences of the `gl-visibility-hidden` legacy CSS util to
Tailwind's `gl-invisible`.

Users of GitLab Community Edition can now
see the Storage Usage Quotas for the
projects under a user namespace

Changelog: changed

identity_verification SaaS feature should be available before a user can
access Opt-in Identity Verification feature.

When block seat overages is enabled and the namespace is over the
number of seats in its subscription, it becomes read-only.
Reject git push operations, adding commits via Web IDE, and merging
MRs when the namespace is read-only for this reason.
Block seat overages work is behind a feature flag.

Add All branches and All protected branches to branch
rule dropdown for creating rules.

This syncs changing the state from opened to closed for epic work items
to the legacy epic when the feature flag is enabled.

It's a scaffold for product usage activity tracking
for GitLab early access program. Only for participants
of the program and only who agreed on optional tracking.

Changelog: added

Delete `Epic::RelatedEpicLink` whenever an associated 
`WorkItems::RelatedWorkItemLink` is deleted.

Using RSpec::Parameterized's `ref` allows referencing `let` binding with
`where` blocks without evaluating them.

Adds a full log viewer for completed logs to the job details page.

Changelog: added

- add new backend flag to determine if instance settings are GitLab-managed provider
- update frontend logic to allow inheriting, depending on provider type
- includes new checkbox on frontend for explicit selection of instance vs project
- update tests

Changelog: fixed
EE: true

Gitaly's transaction support is being rolled out. Prior to the roll
out, we want to exercise the transaction support in Rails pipeline.

Transactions introduce partitioning to Gitaly. Transactions aren't
allowed to do cross-partition operations on the file system. Object
pooling involves the file system level operations against the other
repositories in the same fork network. They need to be thus in the
same partition for the operations to work. Gitaly automatically
places the object pool and the forks in the same partition with the
origin repository as long as they are created using CreateObjectPool
and CreateFork. Rails specs are not doing this currently everywhere
which leads to test failures due to the specs attempting to do
cross-partition operations.

Update the specs to use CreateObjectPool and CreateFork where needed.

- Adds frontend to correspond with backend MR (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147697)

Changelog: added
EE: true

This MR removes the support for match_on_inclusion
on scan_result_policies

Changelog: removed
EE: true

When block seat overages is enabled, the number of billable users in
the group cannot exceed the number of seats in the subscription.
Reject importing members from another project if there are not enough
available seats in the subscription.
Block seat overages is behind a feature flag.

- ensure test coverage for further refactorings during
  work on https://gitlab.com/gitlab-org/gitlab/-/issues/443674