Inventory
(UXPROD-785)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Inventory |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Charlotte Whitt | Assignee: | Charlotte Whitt |
| Resolution: | Done | Votes: | 0 |
| Labels: | elastic-search, metadatamanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||||||
| PO Rank: | 56 | ||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R2 | ||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||
| Description |
|
Overview: Request from Chalmers: Developer comments by Jakub Skoczen: Search on item barcode result in one item barcode. There is a user requirement to have the item record displayed directly, and users want to skip the display of the 2nd pane, and the instance with item detailed list in the top. Display when we have implemented the hierarchical display of the result list: |
| Comments |
| Comment by Julian Ladisch [ 26/Jun/20 ] |
|
I disagree with the proposed solution (extend the back-end keyword index) for the reasons given in
|
| Comment by Theodor Tolstoy (One-Group.se) [ 18/Sep/20 ] |
|
Charlotte Whitt, what are the next steps for this ticket? |
| Comment by Lisa Sjögren [ 02/Nov/20 ] |
|
Hi! How is work on this ticket going? |
| Comment by Charlotte Whitt [ 02/Nov/20 ] |
|
Hi Lisa Sjögren This feature didn't get that high of a calculated total rank (as of today only 52 points). The work has not been prioritized by cap.mvp. What I can do is assigning the feature the new label 'elastic-search'. If easy to fix when implementing Elastic Search in Inventory, then we might be able to loop in the work. But that will be a decision for Magda Zacharska and the Elastic Search development team. |
| Comment by Lisa Sjögren [ 02/Nov/20 ] |
|
Thanks Charlotte Whitt! |
| Comment by Charlotte Whitt [ 08/Nov/21 ] |
|
Holly Mistlebauer - this feature is a low hanging fruit to implement, now we have done
Maybe we could have the work squeezed in for Lotus? |
| Comment by Charlotte Whitt [ 19/Apr/22 ] |
|
Comment to myself and Oleksiy_Lemeshko:
|
| Comment by Charlotte Whitt [ 19/Apr/22 ] |
|
|
| Comment by Khalilah Gambrell [ 13/Feb/23 ] |
|
Hey Charlotte Whitt if this feature requires mod-search work then it will need to move to another release. |
| Comment by Charlotte Whitt [ 14/Feb/23 ] |
|
Okay, I'll assign the ticket to Spitfire, np Khalilah Gambrell |
| Comment by Khalilah Gambrell [ 28/May/23 ] |
|
New feature will be created for Phase 2 |