Skip to content

Add uniqueness check on `topic_id` in the scope of `project_id`

Manoj M J [PTO - Back on 17th June] requested to merge 424778-adding-existing-topic-to-project-redirects-to-500-page-due-to-case-sensitivity into master

What does this MR do and why?

More details in #424778 (closed).

Currently, when a topic of the same name (but in a different case) is added to a project, it fails with 500 error.

This is because there is no uniqueness constraint at the Rails level to catch this problem and show an error on the page itself, rather than the 500.

This MR adds this uniqueness constraint, so the page on an update looks like this now, instead of throwing a 500:

Params Response
Screenshot_2024-01-09_at_12.15.47_PM Screenshot_2024-01-09_at_12.15.57_PM

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #424778 (closed)

Edited by Manoj M J [PTO - Back on 17th June]

Merge request reports