Uploaded image for project: 'mod-orders'
  1. mod-orders
  2. MODORDERS-582

Encumbrances not updated when several encumbrances are changed

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 12.2.1
    • ACQ Sprint 125, ACQ Sprint 126
    • 2
    • Thunderjet
    • R3 2021 Bug Fix

    Description

      Overview: Encumbrance not updated when the following changes are made to POL

      Steps to Reproduce:

      1. POL is opened with $3 cost and no encumbrances
      2. User adds $2 Fund A and $1 Fund B to POL and encumbrances are created.
      3. User edits POL again and removes Fund B, updates Fund A to $3 and saves
      4. Fund B encumbrance is deleted but Fund A encumbrance is not updated.

      Expected Results: Encumbrance values are updated according to estimated price and Fund distributions present at save and close

      Actual Results: Encumbrance value is not updated 

      Additional Information: 
      URL:

      Interested parties:

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Task - A task that needs to be done. MODORDERS-570 MODORDERS (mod-orders) release

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

            Task - A task that needs to be done. MODORDERS-603 MODORDERS (mod-orders) R3 Bugfix release

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

            Bug - A problem which impairs or prevents the functions of the product. MODORDERS-567 Encumbrances not updated after poline currency is changed

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

            New Feature - New feature requests UXPROD-3060 Thunderjet - R3 2021 Tech Debt, NFR

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFIN-207 Create business API for removing Encumbrance transactions

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            has to be finished together with

            Bug - A problem which impairs or prevents the functions of the product. MODFIN-217 Incorrect usage of all-or-nothing mechanism while removing transactions

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-260 Transaction summaries are not designed to be used in parallel

            • 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. MODFISTO-266 Create a new model "TempTransaction"

            • 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. MODFISTO-267 Update table "order_transaction_summaries"

            • 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. MODINVOICE-307 Update transaction summary API calls

            • 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. MODORDERS-581 Update transaction summary API calls

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

            Bug - A problem which impairs or prevents the functions of the product. MODFISTO-259 Releasing 2 transactions at the same time can fail to update budgets

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFISTO-260 Transaction summaries are not designed to be used in parallel

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

            Page Loading...

            Activity

              People

                dennisbridges Dennis Bridges
                andriy_kundyukov Andriy Kundyukov
                Dennis Bridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases