Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Ticket

Details

Notes

Cause

Takeaways/Next Steps

Jira Legacy
serverSystem Jira
serverId0ff96486-f711-332c-a18e-be3fd600929c
keyCUS-15887

Contributors can add B&S Sections. They should have view-only access to the sections Prod

  • Add section, not the entry

  • Missed by Dev and QA team throughout

    • This was included in the acceptance criteria

  • Dev team needs to walk through the Acceptance Criteria more deliberately in refinement

  • Kim to investigate checklists on Jira Tickets

    • Why is a Checklist different than the acceptance criteria?

      • It helps folks slow down

      • We need to develop a process for this if we move forward

Jira Legacy
serverSystem Jira
serverId0ff96486-f711-332c-a18e-be3fd600929c
keyCUS-15886

Contributors can change Sections for their entries that they do not have access toProd

QA: Not an issue at the time, because it was still in dev but reported in 2 places:

2024/12/03 Analisis made by QA and shared in teams.

2024/12/10 reported in CUS-13587

QA updated in the comments of

Jira Legacy
serverSystem Jira
serverId0ff96486-f711-332c-a18e-be3fd600929c
keyCUS-13587

Dev: User stories needs to be broken down more in refinement and in advance (

Jira Legacy
serverSystem Jira
serverId0ff96486-f711-332c-a18e-be3fd600929c
keyCUS-13587
)

Team needs to raise red flag further in advance

Estimates need to reflect planning on working on one story at once

Jira Legacy
serverSystem Jira
serverId0ff96486-f711-332c-a18e-be3fd600929c
keyCUS-15885

Contributors can change the categories on an incident that they should not have access toProd

QA: Not an issue at the time, because it was still in dev but reported in 2 places:

2024/12/03 Analisis made by QA and shared in teams.

2024/12/10 reported in

Jira Legacy
serverSystem Jira
serverId0ff96486-f711-332c-a18e-be3fd600929c
keyCUS-15882

Field content is not left-aligned and is missing commasProd

Questions

  • Defects were marked as done, but the bug was found on production - what happened?

  • Fixes in test were not pushed to load - what happened?

  • Triage issue discovered that was previously fixed. Why was this promoted?

    image-20250130-204136.pngImage Added

Takeaways from the Deployment Meeting

...

  • Confusion within comment conversations

    • How do we document solutions for specific issues agreedupon in conversation in tickets or via Teams?