Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2597

Add option to set transaction status when recording payment

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.6.0-b1
    • Component/s: None
    • Labels:
      None

      Description

      See https://www.blesta.com/forums/index.php?/topic/10932-set-status-when-recording-new-payment/&tab=comments#comment-58162

      When recording a payment in the admin UI, the payment transaction defaults to the 'approved' status, and is automatically applied to the selected invoice(s).

      This should be updated such that

      1. A Status field should be added to the page underneath Currency
        • Include all transaction statuses in the list. Default to 'Approved', the current behavior
      2. If the Status is selected to be any value that is not Approved, the invoices table should be hidden
        • The Email Receipt field should be hidden as well
      3. Once submitted, the transaction should be created in the desired status, but unless it is Approved, it cannot be applied to any invoices
        • The 'payment_manual_approved' email template (i.e. when Email Receipt is checked) should not be sent unless the transaction is approved

      This will allow an admin to add, for instance, old transactions to the system for a client, or transactions collected from another source, but which should not be approved. This also allows an admin to create pending transactions while check payments remaining pending with the bank until they clear and the admin can manually update the transaction status to approved.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            tyson Tyson Phillips (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              28/May/19

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 hour, 7 minutes
              1h 7m

                Agile