Ordering functionality that FOLIO needs to stay competitive
(UXPROD-3440)
|
|
| Status: | In Progress |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Quesnelia (R1 2024) | Parent: | Ordering functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Dennis Bridges | Assignee: | Björn Muschall |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | acq-dev-estimate, acq-morningglory-candidate, acquisitions, needs-ranking | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Ordering functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Leipzig | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 45 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 85 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Mainz (Full TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: MI State-Lib of MI (Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Martina.Schildt [ 10/Mar/21 ] |
|
Dennis Bridges GBV would need to be able to capture statistical data (via custom fields) in Receiving App/on the receiving record. So for us custom fields would be needed in both apps, Orders and Receiving. Is it possible to create a separate feature that we can rank? |
| Comment by Dennis Bridges [ 10/Mar/21 ] |
|
Martina.Schildt I think we may need to discuss this in more detail. As orders and receiving share a BE the custom fields could potentially be shared between the two interfaces. So it may depend if you want to see the custom fields in the "Receiving Title" or in the "piece" record. As both are closely tied to the POL I have added this to the scope of the existing feature for now in hopes that you can rank it accordingly. Would custom fields for receiving be a higher priority? If so it definitely could make sense to split these in some way. thx! |
| Comment by Martina.Schildt [ 12/Mar/21 ] |
|
Dennis Bridges We would need the custom fields on "Receiving title" rather than in the "piece record". If that can be done within this feature that is great, we ranked this with R1 already. In general, having custom fields in receiving is more important for us than having them on the order. |
| Comment by Martina.Schildt [ 09/Feb/23 ] |
|
Hi Dennis Bridges, do you already know when this functionality will be available? It was an MG candidate, but there is no planned fix version given. |
| Comment by Dennis Bridges [ 09/Feb/23 ] |
|
Hi Martina.Schildt this is not currently scheduled. I don't currently have a realistic date so I think it is best to leave the fix version blank for now. This way i'm not creating any false expectations. |
| Comment by Björn Muschall [ 20/Oct/23 ] |
|
According to some libraries a dedicated date field as custom field type is desired. |
| Comment by Björn Muschall [ 01/Nov/23 ] |
|
Dev-team in consultation with Dennis Bridges set on Leipzig. |
| Comment by Khalilah Gambrell [ 19/Dec/23 ] |
|
Hey Björn Muschall will this work be done for the "Q" release? |
| Comment by Björn Muschall [ 19/Dec/23 ] |
|
Khalilah Gambrell Yes, we think that should work. I have set Fix version accordingly. |
| Comment by Khalilah Gambrell [ 19/Dec/23 ] |
|
Thanks Björn Muschall. If there are any custom field related issues that blocks this development then please assign issues to Development = Volaris as this team now owns custom fields functionality. cc: Irina Pokhylets and Dennis Bridges |