Skip to content

Use unique keys for token inputs while add same value twice to an epic

Kushal Pandya requested to merge 4992-fix-token-unique-key into master

What does this MR do?

When same value (or URL of issue) is added twice to an epic, underlying key used for token component is also repeated, leading to situation mentioned in #4992 (closed). This MR adds a method tokeyKey which generates unique token string via _.uniqueId() to prevent collision.

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • [ ] Documentation created/updated
  • [ ] API support added
  • Tests added for this feature/bug
  • Review
    • [ ] Has been reviewed by UX
    • Has been reviewed by Frontend
    • [ ] Has been reviewed by Backend
    • [ ] Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • Internationalization required/considered
  • [ ] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
  • [ ] End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes #4992 (closed)

Edited by Kushal Pandya

Merge request reports