Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rulesets & projects of several clients cannot have the same name #3726

Closed
matthias-ronge opened this issue Jun 4, 2020 · 4 comments · Fixed by #4455
Closed

Rulesets & projects of several clients cannot have the same name #3726

matthias-ronge opened this issue Jun 4, 2020 · 4 comments · Fixed by #4455

Comments

@matthias-ronge
Copy link
Collaborator

matthias-ronge commented Jun 4, 2020

If you create a new ruleset or project in a client (even in a fresh and empty client), you may get an error message that it already exists. This happens, if a ruleset/project with the same name exists in another client − but the user may not have access to that other client. This is confusing and especially annoying when you have to try out several names until you find a free one.

Goal: The same name for the (same) ruleset/project should be possible for each client.

@matthias-ronge
Copy link
Collaborator Author

Related to #3658

@matthias-ronge matthias-ronge changed the title Rulesets of several clients must not have the same name Rulesets & projects of several clients cannot have the same name Jun 2, 2021
@matthias-ronge
Copy link
Collaborator Author

The same problem applies to projects.

@solth
Copy link
Member

solth commented Jun 3, 2021

The same problem applies to projects.

I cannot reproduce the error for projects - I can create multiple projects with identical titles for separate clients.
@matthias-ronge Are you sure it still occurs in the current master?

@matthias-ronge
Copy link
Collaborator Author

The same problem applies to projects.

I cannot reproduce the error for projects - I can create multiple projects with identical titles for separate clients.
@matthias-ronge Are you sure it still occurs in the current master?

I didn’t notice myself, this was reported to me but it was on an older version. I suggest leaving this ticked closed unless we stumble upon the problem again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants