Custom Fields
(UXPROD-396)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD | Parent: | Custom Fields |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Charlotte Whitt | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | delegate_candidate, inventory | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Release: | Not Scheduled | ||||||||
| Epic Link: | Custom Fields | ||||||||
| Development Team: | Spitfire | ||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 3 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||
| Description |
|
Should this be Spitfire or Folijet? Current situation or problem: When we have implemented Custom Fields in Inventory, then these need to be searchable, and necessary search indexes applied. In scope: Search in Inventory by Custom Fields for each of the segments (Instance, Holdings, Item). Use case(s) Proposed solution/stories: Might be solved by using Elastic Search. Links to additional info Questions |
| Comments |
| Comment by Khalilah Gambrell [ 27/Sep/23 ] |
|
Hey Ann-Marie Breaux. This would be Spitfire. |