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

Allow Request Policy to Control Request Fulfillment Options

    XMLWordPrintable

Details

    • New Feature
    • Status: Draft (View Workflow)
    • P4
    • Resolution: Unresolved
    • None
    • None
    • None
    • Hide
      Cate Boerema: Simplest solution would be to rely on the flag on the user record that says whether a given user can have items delivered or not (see draft mockup here: https://drive.google.com/drive/folders/1lqjdblpO_3wFLYcZdR4jabGCmp0iFsmC) This is less sophisticated than using request policy which looks at user as well as the item, but it might be sufficient for mvp.
      Show
      Cate Boerema: Simplest solution would be to rely on the flag on the user record that says whether a given user can have items delivered or not (see draft mockup here: https://drive.google.com/drive/folders/1lqjdblpO_3wFLYcZdR4jabGCmp0iFsmC) This is less sophisticated than using request policy which looks at user as well as the item, but it might be sufficient for mvp.
    • Large < 10 days
    • XL < 15 days
    • Low
    • Hide
      CB: Per discussion with the cap planning team, some of use non-developers are estimating features to avoid disrupting development. I will tag this as "swag" so we know to come back and revisit later when we have more info and are closer to development.
      Show
      CB: Per discussion with the cap planning team, some of use non-developers are estimating features to avoid disrupting development. I will tag this as "swag" so we know to come back and revisit later when we have more info and are closer to development.
    • Vega
    • 16
    • 28
    • 2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
    • R4
    • R4
    • R4
    • R1
    • R4
    • R4
    • R4
    • R2
    • R4
    • R4
    • R4
    • R1
    • R1
    • R4

    Description

      The first version of the request policy only allows you to specify what types of requests are allowed for the requester/item combination.

      This feature is about adding a section to the request policy to control fulfillment options. Current thinking on design of this section:

      Old mockup of full blown request policy (for context): https://drive.google.com/drive/folders/12lN1MV7MZPU2NicldGC-y6orGgY_mR5v

      TestRail: Results

        Attachments

          Issue Links

            relates to

            New Feature - New feature requests UXPROD-113 Fulfilling delivery requests

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

            New Feature - New feature requests UXPROD-2689 Enable Request Policy to Determine Allowed Pickup Service Points

            • TBD - To be determined
            • In Refinement

            New Feature - New feature requests UXPROD-2690 Prevent Local Page Requests

            • TBD - To be determined
            • Draft

            Activity

              People

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

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases