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

Allow Request Policy to Control Request Fulfillment Options

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
      UXPROD features
    • Potential Workaround:
      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.
    • Epic Link:
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XL < 15 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      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.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      45
    • Kiwi Planning Points (DO NOT CHANGE):
      16
    • PO Rank:
      28
    • PO Ranking Note:
      2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: Grand Valley (Full Sum 2021):
      R2
    • Rank: hbz (TBD):
      R4
    • Rank: Hungary (MVP End 2020):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      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

              Activity

                People

                Assignee:
                brookstravis Brooks Travis
                Reporter:
                cboerema Cate Boerema
                Front End Estimator:
                Cate Boerema Cate Boerema
                Back End Estimator:
                Cate Boerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases