@Khalilah Gambrell @Stephanie Buck Ok. I've tested this coming in via the edge API, and the level seems to be correct, but it doesn't seem to be respecting request policy at the item level, so the type is wrong (but in-line with https://folio-org.atlassian.net/browse/CIRC-1455#icft=CIRC-1455). One of my attempts should have place a title-level hold, even though there was an available item, because according to the applicable request policy for the item/patron combination, that item was "hold-only". The fix for that is, apparently, awaiting work for https://folio-org.atlassian.net/browse/CIRC-1479#icft=CIRC-1479, which is still in-progress. I just wanted to make sure that was noted. Going to mark as done.

Thanks, Oleksandr. I've moved https://folio-org.atlassian.net/browse/CIRC-1455#icft=CIRC-1455 to lotus bug fix release so we can test both request type and request level. 

@Stephanie Buck this ticket does not really fix anything, it's an implementation of a feature. And it does decide request of which type to create (although I did miss this validation which is fixed in https://folio-org.atlassian.net/browse/CIRC-1455#icft=CIRC-1455). So I think the description is still valid. I linked the two tickets together.

Thanks, @Oleksandr Vidinieiev. That's interesting. I'm not sure what to do with https://folio-org.atlassian.net/browse/CIRC-1455#icft=CIRC-1455 right now, but this ticket describes fixing both title level and request type. We should update this ticket and maybe link it to https://folio-org.atlassian.net/browse/CIRC-1455#icft=CIRC-1455 in the meantime. 

@Stephanie Buck this issue was fixed in https://folio-org.atlassian.net/browse/CIRC-1455#icft=CIRC-1455 which is R2. Should we release it as R1 Bugfix?