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

Close order and identify a reason for closure

    XMLWordPrintable

    Details

    • Template:
    • Analysis Estimate:
      Small < 3 days
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      Medium < 5 days
    • Development Team:
      Thunderjet
    • Calculated Total Rank:
      110
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: hbz (TBD):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      Purpose: Users need the ability to resolve orders by closing them and indicating a reason for closure.

      High Level Requirements:

      • The system will also need to close orders and identify a reason for closure in certain situations. Eg. All associated PO Lines have been closed.
      • Purchase Order Lines will be considered closed when they have been fully received and fully paid. Our when they are marked as receipt not required and payment not required.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                dennisbridges Dennis Bridges
                Reporter:
                dennisbridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases