Uploaded image for project: 'ui-requests'
  1. ui-requests
  2. UIREQ-368

Include effective call number elements in the Hold shelf clearance report

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 34
    • 1
    • Vega

    Description

      Purpose: To include the effective call number elements in the Hold shelf clearance report.

      User story:
      As a user who has exported a list of items that need to be cleared from the hold shelf
      I want to see all the effective call number data and have it display as separate columns
      So I can sort and filter them individually

      Scenarios:

      1. Scenario
        • Given the Hold shelf clearance report
        • When exported
        • Then the existing "Call number" column should be removed and replaced with the following columns:
          • Effective call number prefix
          • Effective call number
          • Effective call number suffix
          • Volume
          • Enumeration (already exists as a column in the export)
          • Chronology
          • Effective copy CB: We don't have Effective copy so let's use Item copy instead

      Note: A separate story will be added for including the machine sortable call number in this report

      TestRail: Results

        Attachments

          Issue Links

            clones

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-367 Include effective call number elements in the Request CSV

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            defines

            New Feature - New feature requests UXPROD-2173 Display Effective Call Number Throughout Requests App

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is blocked by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-546 UIREQ-368: Backend for adding effective call number to Hold shelf clearance report

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-357 Store effective call number on item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-358 Store effective call number prefix on item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-360 Store effective call number suffix on item record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                annamelnyk Anna Melnyk
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases