Deprecate non-nullable target field on Todo in favor of nullable target_entity

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Under certain circumstances like the need for SAML-reauthentication, the target on a TODO can be null.

Unfortunately the target field is not nullable, so we created a new one target_entity which is nullable.

Click to expand

Labels

This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
- A deprecation announcement entry has been created so the deprecation will appear in release posts and on the general deprecation page.
- Documentation has been updated to mark the feature as deprecated.
On the major milestone:
- The deprecated item has been removed.
- If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.

Mentions

Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
- To see who the stable counterparts are for a product team visit product categories
  - If there is no stable counterpart listed for Sales/CS please mention @timtams
  - If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
  - If there is no stable counterpart listed for Marketing please mention @cfoster3
Your GPM or Director has been @mentioned so that they are aware of planned deprecations.

Edited Sep 15, 2025 by 🤖 GitLab Bot 🤖