Ticket | Details | Notes | Cause | Takeaways/Next Steps |
|---|---|---|---|---|
CUS-15887 - Getting issue details... STATUS | Contributors can add B&S Sections. They should have view-only access to the sections | QA: Not an issue at the time, because it was still in dev but reported in 2 places: 2024/12/03 Analysis made by QA and shared in teams. | ||
CUS-15886 - Getting issue details... STATUS | Contributors can change Sections for their entries that they do not have access to | 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 | ||
CUS-15885 - Getting issue details... STATUS | Contributors can change the categories on an incident that they should not have access to | 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-15882 - Getting issue details... STATUS | Field content is not left-aligned and is missing commas |
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?
Takeaways from the Deployment Meeting
Need a time-effective solution for testing the version that goes live from load test.
Automated testing?
Full regression testing is not advisable
Confusion within comment conversations
How do we document solutions for specific issues agreedupon in conversation in tickets or via Teams?
Add Comment