• Release Candidates

  • Code Review

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-434

      • 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. 

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-649

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-644

      • Back with Steve for final review hopefully

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-645

  • QA / UAT

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-642

       

    • Jira Legacy
      server System

      Jira

      JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-571

       / 

      Jira Legacy
      server System

      Jira

      JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-647

      • Pending Owen

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-654

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-669

• Items at Risk / Spillover
  • Open / Sprint Backlog

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-427

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-655

      • Needs web-toolkit access

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-671

  • In Progress

    • Jira Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-619

      • Confirmed as clear to go (no technical or user dependencies)

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-633

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2081

      • 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

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-652

      • 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. 

    • Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-619

Raised

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-673

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-672

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-676

Brought into sprint: 

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-675

TBC.  

• Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-668

  • 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