@Tino R. @Björn Muschall what work was done for Ramsons release? Can the remaining work be moved to another feature that is assigned to another release?

@Khalilah Gambrell I’ve now added https://folio-org.atlassian.net/browse/UXPROD-5049 as umbrella for related Volaris stories. Feel free to move or change title/content as necessary.

@Khalilah Gambrell Custom fields in orders could only be implemented with code workarounds due to the circumstances described in the two Volaris stories. As long as these circumstances exist, the workaround exists. To clean up the code and remove workarounds, it would be desirable if these issues were tackled in Ramson. If not, the workarounds will continue to exist, which has no negative impact on functionality in Orders for end users. We plan to implement custom fields in other apps as well (but no specific planning so far). We would only do this once https://folio-org.atlassian.net/browse/FCFIELDS-42 and https://folio-org.atlassian.net/browse/FCFIELDS-45 have been resolved.

Volaris stories can be moved to another feature. Would you like to do this? Not sure where and how exactly.

Thank you @Björn Muschall - can we move the Volaris stories to another feature? Also

• Is this story required for Ramsons release of this feature: https://folio-org.atlassian.net/browse/MODORDSTOR-405

• Also what is the impact of not completing these two stories in Ramsons?

  • https://folio-org.atlassian.net/browse/FCFIELDS-42

  • https://folio-org.atlassian.net/browse/FCFIELDS-45

@Khalilah Gambrell @Dennis Bridges https://folio-org.atlassian.net/browse/MODORDSTOR-392 is in Code Review. It would be great if Thunderjet could review related Pull requests in order to close this issue. @Khalilah Gambrell All other related issues above are assigned to Volaris but are not required to close this issue.