This migration marks the 20241105111645 AddWorkItemTypeCorrectId Advanced search migration as obsolete.

[Search for references to `add_work_item_type_correct_id` in code](https://gitlab.com/search?project_id=278964&scope=blobs&search=add_work_item_type_correct_id&regex=false))

At the moment, the `gitlab-housekeeper` is not always capable of removing all references so
you must check the diff and pipeline failures to confirm if there are any issues.
It is the responsibility of the assignee (picked from ~"group::global search") to push those changes to this branch.

[Read more](https://docs.gitlab.com/ee/development/search/advanced_search_migration_styleguide.html#cleaning-up-advanced-search-migrations)
about the process for marking Advanced search migrations as obsolete.

All Advanced search migrations must have had at least one
[required stop](https : // docs.gitlab.com / ee / development / database / required_stops.html)
to process the migration. Therefore we mark any Advanced search migrations added before the
last required stop as obsolete.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::MarkOldAdvancedSearchMigrationsAsObsolete keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other
EE: true

This is used by Duo Workflow for storing intermediate checkpoint data
when interrupting a workflow.

Changlog: added

* Bulk schedule vulnerability statistics.
* Bulk schedule synchronization of findings to approval rules.

Remove some of the default organization references from oauth related
code.

Related: #428018

Changelog: changed

We're moving the expression parsing to a public method so that it can be
used in the JSON export service.

- if a custom role is used in a security policy, then it should not
  be able to be deleted
- disable delete button if it is used in a security policy on
  the frontend
- if there are dependent security policies, we use a
  popover instead of a tooltip
- update tests

Changelog: added

EE: true

In order to be able to order the records by
`verified_at` and `last_synced_at`, add an index
on each field, for each table.

EE: true
Relates to: #514998

* Add model validation
* Add NOT NULL constraint to vulnerabilities.detected_at column
* Schedule NOT NULL constraint validation

Changelog: added

This commit changes 'user_count' with 'seats'
in license.rb and license_spec.rb

Changelog: other
EE: true

Context
----------------------

After a gap analysis of the features available on the group and
project level dependency pages[^1], we have begun work to bring the
pages to parity.

It appears the same [finder][0] is used in the [group][1] and [project][2]
controllers. This means that all we need to do for adding a filter or
sort param is:

1. add the new param to the controller's permitted params
2. add spec coverage

This change
----------------------

1. Adds the `licenses` key as a valid filter param
2. Adds a spec making sure the controller is wired up properly to the finder[^2]

[^1]: There is a table of the analysis on the [epic][3]
[^2]: More extensive testing of the filtering (e.g. multiple values,
      nil values, etc.) is left to the finder's spec. Here, we are only
      concerned that the parameters are flowing to the finder as expected

[0]:https://gitlab.com/gitlab-org/gitlab/-/blob/0a5af4787ad597d3f1726d3cd00ee93d16c35e2c/ee/app/finders/sbom/dependencies_finder.rb
[1]:https://gitlab.com/gitlab-org/gitlab/-/blob/0a5af4787ad597d3f1726d3cd00ee93d16c35e2c/ee/app/controllers/groups/dependencies_controller.rb#L104
[2]:https://gitlab.com/gitlab-org/gitlab/-/blob/0a5af4787ad597d3f1726d3cd00ee93d16c35e2c/ee/app/controllers/projects/dependencies_controller.rb#L92
[3]:&15305

---

related to: #493773
MR: !179432

This reverts merge request !180090

Changelog: changed
EE: true

Missing thread was causing the Duo Code Review Chat to load the
messages from first thread all the time which is incorrect.
It should load messages from the current thread only.

- cover more cases
- improve readablity

This permission allows members to view the user management pages in the
Admin area.

EE: true
Changelog: added

Changelog: added

EE: true

Fixes bug in Value Stream Analytics where success alert was not being
dismissed upon deleting a newly created/updated value stream.

Changelog: fixed
EE: true

Migrates data from SystemAccess::MicrosoftApplication to
SystemAccess::GroupMicrosoftApplication. This is to enable the table to
be split between instance application records for instance-wide SAML
sync, and per-group application records for group-based SAML sync.

This way we can shard the data appropriately for Cells.

The code will initially write to both tables during the transition, with
a feature flag to control which table is read from. When the feature
flag is removed, we can remove writing to the legacy table.

Changelog: changed
EE: true

Since `work_item_epics_ssot` is already used for other parts of the
code, it's safer to use a separate feature flag for this rollout.

This reverts merge request !177883

Add group or project as sharding key.
Backfill all records in a post deploy migration
as the table is very small

Changelog: other

Sometimes users must reindex or recreate the index to take advantage of
Advanced Search improvements in certain releases. The elastic info rake
task will now output the version in which the index was created.

Changelog: added
MR: !179446
EE: true