This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
Duplicate Plan Names #451
Assignees
Labels
Comments
|
Adding this to Sprint 10. |
|
Looks like it's still up for grabs... going to grab this one next 🤹♂️ |
agrare
added a commit
to agrare/manageiq
that referenced
this issue
Jul 9, 2018
Add a unique name validation, scoped to the tenant, for ServiceTemplateTransformationPlans. ManageIQ/manageiq-v2v#451
agrare
added a commit
to agrare/manageiq
that referenced
this issue
Jul 9, 2018
Add a unique name validation, scoped to the tenant, for ServiceTemplateTransformationPlans. ManageIQ/manageiq-v2v#451
|
@priley86 backend support for name uniqueness validation within a tenant was merged ManageIQ/manageiq#17677 |
This was referenced Jul 9, 2018
AparnaKarve
added a commit
that referenced
this issue
Jul 10, 2018
[#451] duplicate plan name validation
simaishi
pushed a commit
that referenced
this issue
Jul 26, 2018
[#451] duplicate plan name validation (cherry picked from commit 8bf1179) https://bugzilla.redhat.com/show_bug.cgi?id=1608768
jerryk55
pushed a commit
to jerryk55/manageiq-v2v
that referenced
this issue
May 29, 2019
Add a unique name validation, scoped to the tenant, for ServiceTemplateTransformationPlans. ManageIQ#451 (transferred from ManageIQ/manageiq@fb695d0)
jerryk55
pushed a commit
to jerryk55/manageiq-v2v
that referenced
this issue
Jun 3, 2019
Add a unique name validation, scoped to the tenant, for ServiceTemplateTransformationPlans. ManageIQ#451 (transferred from ManageIQ/manageiq@fb695d0)
jerryk55
pushed a commit
to jerryk55/manageiq-v2v
that referenced
this issue
Jun 4, 2019
Add a unique name validation, scoped to the tenant, for ServiceTemplateTransformationPlans. ManageIQ#451 (transferred from ManageIQ/manageiq@fb695d0)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I know the term "duplicate" is starting to make us shriek...
Per our last email on this subject - we would like to use the UI to work around the duplicate plan name issue in the short term by simply checking the service template (plans) in memory (loaded from Overview) and passing them into the Plan Wizard (to allow checking for duplicates). This is a short term fix - the long term fix is obviously adding this validation on the backend.
Would like to resolve this for 5.9.4.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1567225
The text was updated successfully, but these errors were encountered: