Bug 25739 - Add guarantee doesn't link to parent account
Summary: Add guarantee doesn't link to parent account
Status: RESOLVED DUPLICATE of bug 23808
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: 19.11
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-12 21:12 UTC by Christopher Brannon
Modified: 2020-09-20 23:26 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2020-06-12 21:12:02 UTC
All it does is give you a blank minor form to fill out.
Comment 1 Katrin Fischer 2020-06-13 17:16:28 UTC
Hi, I think this might be a misunderstanding between guarantor and garantee?

guarantee replaces the formerly used term "child" and it always linked to an empty patron form and not to a search.

Almost empty: The guarantor information is preset correctly.

I've verified this in an 17.11 and in a master installation.
Comment 2 Christopher Brannon 2020-06-26 17:29:29 UTC
No, there is no understanding.  It creates a new minor (child) record, as expected.  But there is no link to the guarantor (parent) account.  While filling out the child account, you will notice there is no information about the guarantor in the guarantor fields.  And the account is not linked once you finish editing and save.
Comment 3 Owen Leonard 2020-06-26 19:01:06 UTC
Here's what I see when I test in 19.11.x:

1. Open patron detail page for an adult record
2. Click "Add guarantee" button
3. Patron edit form opens. I see:
   - Blank "Patron identity" form fields.
   - "Guarantor information" fieldset with details about
     the adult record I started with.
   - "Main address" and "Contact" fields are filled in
     with information from adult record.
4. I enter the child name and card number, click save.
5. I'm redirected to the detail record for the newly-added
   child account.
6. Under "Guarantor" on this page is the name of the adult
   I started with, linked to that patron's account.
Comment 4 Owen Leonard 2020-06-26 19:36:48 UTC
Also check the value in your PrefillGuaranteeField preference.
Comment 5 Christopher Brannon 2020-06-26 19:53:20 UTC
(In reply to Owen Leonard from comment #4)
> Also check the value in your PrefillGuaranteeField preference.

That is added in 20.05.  We are 19.11.
Comment 6 Christopher Brannon 2020-06-26 19:58:02 UTC
(In reply to Owen Leonard from comment #3)
> Here's what I see when I test in 19.11.x:
> 
> 1. Open patron detail page for an adult record
> 2. Click "Add guarantee" button
> 3. Patron edit form opens. I see:
>    - Blank "Patron identity" form fields.
>    - "Guarantor information" fieldset with details about
>      the adult record I started with.
>    - "Main address" and "Contact" fields are filled in
>      with information from adult record.
> 4. I enter the child name and card number, click save.
> 5. I'm redirected to the detail record for the newly-added
>    child account.
> 6. Under "Guarantor" on this page is the name of the adult
>    I started with, linked to that patron's account.

I am in 19.11.06, and we do not get the "Guarantor information" fieldset with details about the adult record I started with."

Even after I save, it is not linked to the guarantor.
Comment 7 Owen Leonard 2020-06-27 00:11:39 UTC
> I am in 19.11.06, and we do not get the "Guarantor information" fieldset
> with details about the adult record I started with."

I think Bug 23808 fixes this as of 19.11.07.
Comment 8 Katrin Fischer 2020-09-20 23:26:41 UTC
(In reply to Owen Leonard from comment #7)
> > I am in 19.11.06, and we do not get the "Guarantor information" fieldset
> > with details about the adult record I started with."
> 
> I think Bug 23808 fixes this as of 19.11.07.

Marking as a duplicate in this case.

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