Uploaded image for project: 'ERM Platform'
  1. ERM Platform
  2. ERM-877

Require Agreement names to be unique

    XMLWordPrintable

Details

    • ERM Sprint 89, ERM Sprint 90
    • Bienenvolk

    Description

      Agreement names should be unique.

      If a user tries to save an agreement with the same name as an existing agreement, an in-form validation message should be displayed "This name already exists".

      See Settings > Local KB admin > New external data source for an example (shown in screen shot below).

      If existing names need to be migrated to be unique, then they should have a numeric suffix added until they are unique (e.g. "agreement A" and "agreement A" become "agreement A" and "agreement A_1"

      TestRail: Results

        Attachments

          Issue Links

            defines

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-891 Require Agreement Names to be unique (Backend Validation)

            • TBD - To be determined
            • Closed

            New Feature - New feature requests UXPROD-1669 UX improvements for Agreements up to Q3 2020

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-888 Update LAS:eR / Folio integration script to add configurable suffix to agreement name

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ERM-1116 On a 422 error on an attempt to clone an agreement, a specific error should be displayed if available

            • TBD - To be determined
            • Closed

            Activity

              People

                sosguthorpe Steve Osguthorpe
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases