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

Ability to Tag Request Records

    XMLWordPrintable

Details

    • Medium < 5 days
    • Medium < 5 days
    • Hide
      Estimates added by Cate, copied from what I assume is a very similar feature: Tags on Inventory records (UXPROD-274). Actually bumping up to 5 days each instead of 3 since we need to get the Tags into the Requests csv export.
      Show
      Estimates added by Cate, copied from what I assume is a very similar feature: Tags on Inventory records ( UXPROD-274 ). Actually bumping up to 5 days each instead of 3 since we need to get the Tags into the Requests csv export.
    • Prokopovych
    • R1
    • R4
    • R2
    • R2

    Description

      Tags will be useful on Requests for many reasons. For example, to support the pick list workflow using the Requests csv.

      Scenario

      1. Print csv for items to be picked up off the shelves (Request status = Open - Not yet filled and Item status = Available)
      2. Find all but 2 of the items
      3. Mark those two requests/items as not found so they can be filtered out of the next pick list report which may be generated again in an hour or so

      When discussing how best to handle this scenario, we looked at the missing item feature (UXPROD-965) to see if this might be a way to handle it, but Missing changes the Item status which displays to the patrons and would be confusing. Also, most of the time these items are soon found within a day or so.

      Ultimately, we decided that Tags would be a good way to handle this scenario. Ideally you could filter by this tag. But, as long as the tag is displayed in the csv, that should be sufficient for go-live. Aren't Tags handy?

      Please note, there is a feature in the backlog for a "real" pick list report: UXPROD-923

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                cboerema Cate Boerema
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases