Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2173

Display Effective Call Number Throughout Requests App

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • Q1 2020
    • None
    • Small < 3 days
    • Very Small (VS) < 1day
    • Prokopovych
    • R4
    • R1
    • R4
    • R1
    • R1

    Description

      This was split off of UXPROD-1626 (Implement effective logic for call number in Holdings record and inherited to Item records) as it was not completed in Q4 2019, as planned.

      Scope:
      The scope of this feature is to:

      • UIREQ-366 Display effective call number string on the Request record
      • UIREQ-367 Include effective call number elements in the Request CSV
      • UIREQ-368 Include effective call number elements in the Hold shelf clearance report
      • UIREQ-372 Display effective call number string on the Dedicated request queue page

      TestRail: Results

        Attachments

          Issue Links

            clones

            New Feature - New feature requests UXPROD-2172 Call Number Accordion on Item Record

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open
            is defined 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. UIREQ-366 Display effective call number string on the Request 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. UIREQ-367 Include effective call number elements in the Request CSV

            • 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. UIREQ-368 Include effective call number elements in the 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. UIREQ-372 Display effective call number string on the Dedicated request queue page

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

            New Feature - New feature requests UXPROD-1626 Store Effective Call Number Prefix, Call Number and Suffix in the Item Record

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

            Activity

              People

                cboerema Cate Boerema
                cboerema Cate Boerema
                Zak_Burke Zak_Burke
                Bohdan Suprun Bohdan Suprun
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases