• Triage: NA

• Approach
  • Backend
    • add new refdata set for new contentType, called, eg SubscriptionAgreementContentType to keep separate from ContentType
    • Set SubscriptionAgreementContentType 
    • based on new set of refdata, set up domain class, grails view and migration (but not schema)
      • see PR on ERM-2045
      • use curl/postman to attempt to bind contentType to determine whether internal or external
    • uses existing mechanisms for refData and contentType handling mechanisms
    • may need to bump migration number if dropping tenant doesn't just work
      • can comment out remoteKb bootstrap line to prevent harvest drop
      • or change active status in sample data as per Vagrant Setup for ERM#AvoidGOKbharvesting
  • Frontend
    • set up multi-selection on agreement as per existing patterns
    • add new filter option according to existing patterns

• Components and Changes

  • Frontend: ui-agreements

  • Backend: mod-agreements

• Tests / Data / Dependencies: 

  • update frontend tests, no backend tests needed

• Known Unknowns: none

• QA: snapshot

• Release Target: Orchid

• Development Estimate: Wed/Thu

• Triage

  • Attempt to reproduce this on non-GBV environment
  • Review what is and isn't being populated
    • additional_info is added
    • title is not the expected title (compare wit title in message)
  • Possible that additionalInfo is only updated at certain times?
  • Check whether error log has similar info
  • Disconnect between what and how we are appending, using special Grails sauce
    • error and info not updated together
    • possible race condition
• Approach
  • potentially extend with titleId

• Components and Changes

  • Frontend: NA

  • Backend: mod-agreements

• Tests / Data / Dependencies: 

  • Owen to set up testdata as a json package with errors

• Known Unknowns: NA

• QA: snapshot 

• Release Target: Orchid

• Development Estimate: needs triage and re-learning: review on Wed

1. Set up Jira issue
2. Set up cypress end-to-end test for agreements (Ethan)
   1. check it exists in navbar, and that it shows up 
   2. work out how to run it
   3. use as template for extending within agreements
3. Export Testrails list (Owen)
4. Review for e2e conversion (team)
5. Get Testrails logins (Jag)

 {
        "permissionName": "settings.licenses.enabled",
        "displayName": "Settings (Licenses): Can view and edit settings",
        "subPermissions": [
          "module.licenses.enabled",
          "settings.enabled",
           "configuration.entries.collection.get",
          "configuration.entries.item.put",
          "configuration.entries.item.post"
        ]
      },

No need to worry about export.

• Triage

  • useEffect doing job of mount handler
• Approach
  • can input approach be set up differently?
  • is only one id needed, in which case how would stripes handle this across tabs?
  • persistent results wiped across app-tab switching

• Components and Changes

  • Frontend

  • Backend

• Tests / Data

• Dependencies

• Known Unknowns

  • unknown impacts

• QA: snapshot | local | testing | other

• Development Estimate

• Work to do UUID is done and verified on a new deployment, but not an existing one, for regression testing
• Needs
  • deployment of old code
  • successful harvest
  • deployment of new code
  • delta harvest
• Not clear whether the k-int environment is able to support this regression testing
  • Owen to check with Ian for future utility
• For now, to be tested by screensharing with Ethan on Thu morning