Bug 31880 - "Go to field" link in MARC validation goes nowhere if field not in the same tab
Summary: "Go to field" link in MARC validation goes nowhere if field not in the same tab
Status: RESOLVED DUPLICATE of bug 32523
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
Keywords: regression
Depends on:
Reported: 2022-10-19 18:44 UTC by Caroline Cyr La Rose
Modified: 2023-03-20 13:39 UTC (History)
4 users (show)

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


Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2022-10-19 18:44:09 UTC
I'm having trouble with the "Go to field" link when you don't fill in a mandatory field when cataloging. Normally, it takes you to the field, but now it doesn't seem to do anything if the field is not in the current tab...

To test:
(Note: I did this with the default framework in MARC21, when I refer to fields, they are MARC21 fields and they are mandatory by default in the default framework)
1. Go to Cataloging > New record
2. Click "Save" without filling anything out
   --> You should get a bunch of warnings about mandatory fields that are not filled 
3. Click "Go to field" next to the 245$a error
   --> Nothing happens
4. Click "Go to field" next to the 040$c error
   --> You are taken to 040$c
5. Click on tab 2
6. Click Save again (not sure it's necessary)
7. Redo step 3
   --> You are taken to 245$a
8. Redo step 4
   --> Nothing happens
Comment 1 Katrin Fischer 2022-10-24 21:01:06 UTC
I see the same, when the field is not on tab 0.

Could the switch to Bootstrap tabs have something to do with this?
Comment 2 Laura Escamilla 2023-03-07 14:30:23 UTC
This bug is still relevant in 22.05.09.
Comment 3 Nick Clemens 2023-03-20 13:39:35 UTC
Marking as duplicate of 32523, seems to be fixed now

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