Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

CHEFS = Common HostEd Form Service

How do we create a connected community that can learn and improve together?

  • Sharing our experiences is an important piece of this puzzle, and Weeknotes are an accessible way to achieve this.

  • Weeknotes aim to share lessons learned in a predictable, scannable template.

  • They are a first step to working in an open way that can enhance learning and continuous improvement


📙 CHEFS Team Weeknotes 1

 

  1. Has Been Fixed (Broke No More): Broken things that we fixed  

  • The search tool for adding team members now works with BCeID users using just 4 characters in the search. 

  • Fixed missing tools in our software updates to keep deployment systems working smoothly. For more information on JIRA, click here

  • All backups now run on BCDevOps version 2.9.0, and verified backups have been successfully completed. For more information on JIRA, click here

 

  1. New To The User (Brand New, Secondhand): These are the most exciting because they are new

  1. Has Been Improved (Continuous Improvement Bucket): A conversation about anything and everything that makes the product faster and better 

  • Thanks to the EMLI <insert name> and MCAD <insert name> teams, the original developers of this script, a standalone Python script is now available for downloading submissions with an API key. 

  • The front-end Vue components have been upgraded to the Composition API for better organization, flexibility, and handling of complex components. 

  • Cypress scripts were created to test form creation, role visibility, submissions, and status updates by mimicking user actions. 

  • A new feature lets Form Designers call an External API securely without storing sensitive data like passwords or tokens in plain text. For more details, click here

  1. Future Focus (Boldly Go Where No Common Component Has Gone Before) Feedback on things we have started building  

  • The new map tool lets you place pins, draw circles, or outline areas to show locations or collect geographic information. To test this feature, click here. To look at the techdoc on Git Hub, click here

  • We held our first Common Components Architecture Forum this quarter; click here for more information, including a summary of the morning and afternoon sessions. 

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

 Weeknotes Structure:
  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design

  • No labels