Prevent projects with same slug from having same service desk project key
What does this MR do?
Follow up of !62139 (merged)
This covers an edge case, for projects with same full path slug, for example:
One project group/test-one
and another one group/test/one
will both generate the same slug
group-test-one
. If both have the same service desk project key incoming emails will arrive at the first project created.
This MR adds model validation to prevent the scenario from above.
We should probably skip migrations, in this case, it is better to invalidate records and let users change project keys
manually instead of setting them to nil
which could break the existing service desk workflow.
Error message
related to #300964 (closed)
Edited by Felipe Cardozo