I think that I have a library (and possibly multiple libraries) that may be impacted by this Jira and will likely want to rank this highly as a result. However, I want to verify that I understand what this means so I'm going to outline the behavior we're seeing below. Would you be able to verify that the scenario adheres to this ticket and should not be filed as a separate bug?

A library has a notice template for an overdue notice. The text looks something like this:
 
Dear user.firstName user.lastName,
 __ 
The due date has passed on the item(s) listed below. Fines may be accruing, so please renew online, if eligible, or  return as soon as possible.
 __ 
If this item not renewed or returned, you will be billed for its replacement. Billed items cause borrowing privileges to be suspended without notice until material is returned or replaced or you pay for the material.
 __ 
Author: item.primaryContributor
Title: item.title
Call Number: item.callNumber
Barcode: item.barcode
Date Checked Out: loan.initialBorrowDateTime
Due Date: loan.dueDateTime
 __ 
Thank you for your prompt attention to this matter.
 __ 
Regards,
 __ 
Circulation Staff
 
This intent is to use this template both on short term and long term loans. It seems to work well on short-term notice policies where “Send throughout the day without multiple loans/items. Useful for short-term loans.” is selected. However, on longer term notice policies where “Send overnight with multiple loans/items by patron. Useful for long-term loans.” is selected, the token information does not fill in appropriately. 
 
Does this mean that the library would need to maintain two separate notice templates - one with the multiple loans token and one without - to function in each case?

Is it possible to get some more information on what this ticket means? Thanks.