[Bug][AzureDevopos] When creating a new connection, allowing the same name to exist does not meet the expectations.

[xiaomingzhang12]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Select the Azure DevOps plugin and create a new connection, naming this connection 'Azure'.

Create another new connection, also naming this connection 'Azure'.

Click 'save connection'. The creation is successful. After creating three times, the effect is as shown in the picture:

The problem with this situation is: Based on the current circumstances, it is not easy to select when associating connections with projects.

What do you expect to happen

Expectation: Similar to the handling with the Jira plugin, when the name is the same as an existing connection name, the interface/api/plugins/azuredevops/connections should give an error message. Below is an example from Jira:

How to reproduce

See above

Anything else

No response

Version

main

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[keon94]

@klesh There's no uniqueness index on the name fields of Azure connections. This can be added via migrations but what do you want to do about existing duplicates? We can't really automate deleting them: how do we know which ones to delete? How do you want to tell the user they have to delete duplicates before migrations can proceed? Just error out?

[klesh]

@keon94 I see. How about we rename them automatically? For example, lets say there were 3 "xxx", we could rename them to "xxx" "xxx - 1" and "xxx - 2" before adding the unique index in the migration script. is it doable?

[keon94]

@klesh That's a smart solution. Yes, that should be doable.

[keon94]

PR: #6911