Bug 13467

Summary: acq tab still says ordered even if completed
Product: Koha Reporter: Nicole C. Engard <nengard>
Component: AcquisitionsAssignee: Bugs List <koha-bugs>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: katrin.fischer, marjorie.barry-vila
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Attachments: ordered instead of completed

Description Nicole C. Engard 2014-12-15 14:00:12 UTC
Created attachment 34426 [details]
ordered instead of completed

When an order is completed it's still saying that it's ORDERED in the acq details tab in the staff client.  In the attached image you can see the received date and when I look at the invoice everything is received and done.  It should say completed but does not.
Comment 1 Marjorie Barry-Vila 2015-11-13 16:58:13 UTC
(In reply to Nicole C. Engard from comment #0)
> Created attachment 34426 [details]
> ordered instead of completed
> 
> When an order is completed it's still saying that it's ORDERED in the acq
> details tab in the staff client.  In the attached image you can see the
> received date and when I look at the invoice everything is received and
> done.  It should say completed but does not.

Hi Nicole,

I notice that status of a received order is changing when basket is reopened.

Test plan:
1. receive an item X of basket A, status in acq details tab is Complete
2. reopen basket A, status in acq details tab is now New for item X
3. close basket A, status in acq details tab is Ordered for item X

Is it the same in your case?

Regards,
Marjorie
Comment 2 Katrin Fischer 2015-11-22 22:00:23 UTC
I think this has been fixed by: 
Bug 15036 - Closing and reopening a basket should not alter status of completed orders

I also checked on my installation that it's not a general problem. If you follow all the steps, the order is shown as 'complete' at the end.

*** This bug has been marked as a duplicate of bug 15036 ***