Bug 18621 - After duplicate message system picks category expiry date rather than manual defined
Summary: After duplicate message system picks category expiry date rather than manual ...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: 16.11
Hardware: All All
: P5 - low major (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-17 17:25 UTC by Vinod
Modified: 2017-06-17 15:24 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Bot Control: ---
When did the bot last check this:
Who signed the patch off:
Text to go in the release notes:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vinod 2017-05-17 17:25:44 UTC
After duplicate message system picks category expiry date rather than manual defined, the test is as follows:

1. Try to enter a new member 
2. Give member Expiry date which is more than defined in concern category 
3. If Koha found similar member than pop up a message
4. Select not a duplicate member (New member option)
5. Koha saved the record but the expiry date will pick from category rather than you assigned the member.

6. If the member is new and no message is populated than it will save expiry date as you defined.

Koha version 16.11.07 on debian Jessie installed by package.
Comment 1 Lee Jamison 2017-06-17 15:24:03 UTC
Tested following described steps and appears to still exist on current master.