- labels: --> JFireTrade
- milestone: --> none
- summary: "outstanding"-flag of invoice not correct after invoice is aborted --> "outstanding"-flag of invoice not correct after invoice is aborted
DO NOT EDIT OR ANSWER THIS ISSUE. SEE THE ORIGINAL ISSUE INSTEAD:
https://www.jfire.org/modules/bugs/view.php?id=1841
ORIGINAL REPORTER: alex
From its "created" state an invoice can be "finalized" or "aborted". The workflow of an aborted invoice ends and the user can't change it any more. The "outstanding" flag of an aborted invoice "true"?!? From my point of view an aborted issue should not be considered outstanding.
Thinking about this a little more: What is the outstanding-state of a non-finalized invoice? As fas as I can see it is "true" from the beginning, so a invoice in the state "created" is also "outstanding". I think this should be changed, too. In my opinion an invoice that is not finalized is also not outstanding (and of course an finalized invoice is not oustanding any more when its full amount was paid).
So actually I think fixing that aborted invoices are considered outstanding should be done by making them not-oustanding intially and then changing that flag to "true" when an invoice is finalized?