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

[High] Нейминг для второго ПО - не уникален и повторяет имя первого ПО, а вот третий ПО (и далее) уже уникальны #1585

Closed
AlexeyGirin opened this issue Dec 5, 2023 · 2 comments · Fixed by #1658
Assignees
Labels
bug Something isn't working
Milestone

Comments

@AlexeyGirin
Copy link
Contributor

Environment details (please complete the following information):
JDN v 3.14.30 Back-end v 0.2.58
win10

Describe the bug
Нейминг для второго ПО - не уникален и повторяет имя первого ПО

To Reproduce
Steps to reproduce the behavior:

  1. Откройте плагин на страничке https://jdi-testing.github.io/jdi-light/html5.html (пароль - Roman, Pass - Jdi1234)

  2. Создайте там абсолютно любой ПО
    image

  3. Нажмите +Page Object что бы создать второй ПО
    Появляется выпадушка

Actual behavior
Название второго ПО копирует название первого
image

Expected behavior
Название второго ПО должно быть уникальным - должна добавиться единичка в конце

@AlexeyGirin AlexeyGirin added the bug Something isn't working label Dec 5, 2023
@AlexeyGirin AlexeyGirin added this to the Release 3.15 milestone Dec 5, 2023
@AlexeyGirin AlexeyGirin removed this from the Release 3.15 milestone Dec 6, 2023
@savinovava savinovava modified the milestones: Release 3.16, Release 3.15 Dec 12, 2023
@Iogsotot Iogsotot self-assigned this Feb 6, 2024
@Iogsotot Iogsotot linked a pull request Feb 21, 2024 that will close this issue
@Iogsotot
Copy link
Contributor

#1658
3.15.2

@mobilisf
Copy link

Validated on JDN v 3.15.2 Back-end v 0.2.64 [Local and remote servers]
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: M (5)
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants