Uploaded image for project: 'ui-orders'
  1. ui-orders
  2. UIOR-129

Settings: display system-supplied reasons for closure in settings area

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      ACQ Sprint 60
    • Story Points:
      3
    • Development Team:
      Thunderjet

      Description

      Purpose: So that the user can see the system pre-defined reasons for closure when entering tenant-specific reasons for closure

      As a staff person
      I want to be able to see the system's pre-defined reasons for closing an order when I am creating library-specific reasons for closure
      So that I don't create duplicate or overlapping reasons for closure

      Dennis Bridges - please review red questions below, finalize, and change from draft to open

      Scenarios

      1. Scenario 1
        • Given Settings/Orders/Closing Purchase Order Reasons
        • When a User views the list of existing reasons
        • Then include the system-supplied reasons as well as the tenant-supplied reasons.
        • the list should appear in alphabetical order, with all reasons interfiled.
        • System-supplied reasons should NOT be editable/deletable by the user.
        • There should be an indication of which reasons are system-supplied versus user-supplied. Other apps solve this by having another column for the source. See screenshot from inventory settings attached

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Tester Assignee:
                Ann-Marie Breaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases