"Current" status is being used to test logic, which may cause internationalisation problems, if using label/value. 

• To avoid this, would need a feature to configure {agreement/link} status
• Ideally, we distinguish between configurable vs editable refdata

•  Jag Goraya Create new issue to define, for each refdata set, whether configurable/editable, and implications  

TODO:

• BE: Store amendment link status and notes (1d)
  • mirror how license links are handled
  • nested rather than at same level to support easier front-end handling
  • amendment link array, with amendments sorted in start date descending order
• FE: implement form and error (3d)

BE: 0.5d FE: 0.25d

TODO:

• Extend existing filters to include date range
• Missing dates are treated as included, so would need to include NULL check
• FE: update calls to revised endpoints

Existing pattern of counts logging - number of upserts 

Non-trivial maybe is handling single title services

• Is this person AND role, or is it person OR role?

Estimate: 2d

Aim to prioritise to meet module release deadline to include in Daisy release.