• Release Candidates

  • Code Review

    • ERM-434 - Getting issue details... STATUS
      • Reviewed, pending ERM-644 to merge ahead of QA.
      • However, held up in Jenkins. Needs to be re-run by Claudia ({{git commit amend}}).  Currently being  rejected. 
    • ERM-649 - Getting issue details... STATUS
    • ERM-644 - Getting issue details... STATUS
      • Back with Steve for final review hopefully
    • ERM-645 - Getting issue details... STATUS

  • QA / UAT

    • ERM-642 - Getting issue details... STATUS  

    • ERM-571 - Getting issue details... STATUS  /  ERM-647 - Getting issue details... STATUS

      • Pending Owen
    • ERM-654 - Getting issue details... STATUS
    • ERM-669 - Getting issue details... STATUS
• Items at Risk / Spillover
  • Open / Sprint Backlog
    • ERM-427 - Getting issue details... STATUS
    • ERM-655 - Getting issue details... STATUS
      • Needs web-toolkit access
    • ERM-671 - Getting issue details... STATUS
  • In Progress
    • ERM-619 - Getting issue details... STATUS
      • Confirmed as clear to go (no technical or user dependencies)
    • ERM-633 - Getting issue details... STATUS
    • UXPROD-2081 - Getting issue details... STATUS
      • Front end done
      • Fields added to domain model
      • Import code is wizardry - need Steve's input
      • JSON schema provided for the domain model.
      • Still need clarity on business rules and data validation rules
    • ERM-652 - Getting issue details... STATUS
      • Advance notice of breaking changes fro Acquisitions team
      • Orders interfaces are changing. 
      • New support for packages on POL record. 
      • Cannot merge ahead of time because of snapshot process
      • Changes ready to go, but need to be held until Acquisitions are ready to merge later on 22 Jan
      • Backend boxes need to be updated locally as of builds on 23 Jan for Orders 9.0
      • Not currently planning to do a formal ui-agreements version release. 
    • ERM-619 - Getting issue details... STATUS

Raised

• ERM-673 - Getting issue details... STATUS
• ERM-672 - Getting issue details... STATUS
• ERM-676 - Getting issue details... STATUS

Brought into sprint: 

• ERM-675 - Getting issue details... STATUS

TBC.  

• ERM-668 - Getting issue details... STATUS
  • developer preference is to follow the recipe for making complex queries that is ERM-specific, rather than a generic solution
  • so, no reusable component, but the ux pattern should be reusable
  • SAS filters are up for review / re-design
  • may need to be run against the ERM usergroup, which could delay 
  • potentially use popup filters, though this has accessibility issues 
  • need a PO requirements review, then a UI feasibility review
• Lazy loading readiness
  • Aditya matukumalli looking at applying this to ui-agreements, based on ui-users work shared by Victor
  • Initially looking at agreement view/edit, but potential application (eventually) for areas such as eresources in agreement
  • Net benefit is faster loading / performance