# data[].attributes.body
https://kb.uwm.com/display/SERVNOWADMIN/2026-01-19+-+Sprint+111

# data[].attributes.body
Who do you think has the most apps installed on their phone, and why.

# data[].attributes.headline
Write your ideas from the Action Item here

# data[].attributes.subject
Write your ideas from the Action Item here

# data[].attributes.headline
STRY0013118 - Auto-close unapproved RITMs after temporary access end date has passed

# data[].attributes.subject
STRY0013118 - Auto-close unapproved RITMs after temporary access end date has passed

# data[].attributes.body
This is pointed at 2; I would like for 3 to be considered. Created new notification, event, email template, and scheduled script execution. The reason I'm requesting a one point increase is for the testing that's involved - must use a background script for every temporary request to set the date in the past before the script can be manually executed. Must test against past dates and future dates for temporary and permanent requests and have the RITM and the sysapproval_approver table open to ensure the approvals are canceling (or not) and then monitoring email notifications to ensure they are firing correctly. Linda

# data[].attributes.body
Our standups are getting lengthy and having a day in the middle would allow for better updates to work assigned.

# data[].attributes.body
It seems that not everyone is adhering to the rule of posting their questions in the admin or dev channel. Should we disregard this process, or should those who are following the rule continue to do so consistently while others ask directly? I understand that this may vary from person to person. Could we clarify who must post in the channels and who is allowed to ask questions directly?

# data[].attributes.headline
Documentation Scrum Task on Non-Update Set Tickets?

# data[].attributes.subject
Documentation Scrum Task on Non-Update Set Tickets?

# data[].attributes.body
Is the documentation scrum task really needed for queue tickets without an update set? I haven't ran into a time where I needed to write a KB for a update made in Production.

# data[].attributes.body
Despite the lack of clear input on the required changes and the need for multiple discussions with Vendor Relations, successfully completing all updates to contract management is impressive.

# data[].attributes.body
If a story was tested a while ago but never committed, it’s a good idea to retest it before moving forward. With that time gap, there’s a real chance other changes in the system may have affected how it behaves. Retesting helps make sure nothing unexpected has broken in the meantime. It also prevents issues that might show up only after deployment. Plus, it keeps new work from piling on top of something that hasn’t been properly released yet. Overall, giving it a fresh round of testing keeps everything cleaner and more reliable.

# data[].attributes.body
Great job in your first 3 amigos session!

# data[].attributes.body
It's wonderful to see my AAA agents performing exceptionally well on the team and putting forth their best effort every day!

Anna, Anushka & Avery!

# data[].attributes.body
As part of testing the Separation Automation, I had to run through a test case for Vivek's work as well. Hamza was great at diving into every little thing I found and investigating if it was related to his or Vivek's work, or if the error was unrelated at all.

# data[].attributes.body
Thank you for picking up my request to update the BA report/email and working through it with me. This helps us stay on top of any urgent stories!!!

# data[].attributes.body
You are doing an AWESOME job absorbing knowledge about troubleshooting MID/API performance. I know you have an incredibly good memory when you're taught something, so I can not wait to see you use it in the future and teach others! Thank you SO much for being eager to take on the work!

# data[].attributes.body
Thank you so much for always taking time out of your busy schedule to answer questions for the team. You are always there in the admin chat and I am always learning something new from you! :)

# data[].attributes.body
Lauren helped me find what was setting one of fields to read-only and saved me so much time. I would've been stuck on this story for so much longer. I really appreciated her help. Thank you Lauren!!

# data[].attributes.body
You did excellent work on creating the reports for the SSG SLA dashboard and refining the dashboard based on his feedback

# data[].attributes.body
Krishna, thank you for taking the time to help me understand some HAM workflows and for helping me out with this mobile phone story. I really appreciate it!

# data[].attributes.body
i've been reviewing the blocked stories each morning for Fakiha and since i started every single Admin has made huge improvements in this area. i just wanted to recognize everyone's effort to make this a focus and get better.

# data[].attributes.body
Appreciate your thoroughness on CRs. At the end of the day it just makes us all better!!

# data[].attributes.body
Thank you to everyone who helped with testing while I was out of office last week!

# data[].attributes.body
We try to keep a good relationship with stakeholders that we often work with frequently, and it doesn't look so well if I am working with a stakeholder and can't answer a question regarding a different request because I wasn't aware.

For any request that comes from Vendor Relations & Change Managers Could everyone include me in the chats or cc on emails or if walk ups just let me know what happened so when they ask me a question I am not left in the dark. I don't need to be involved in the communication of EVERY request and step on toes especially if they are queue requests, but it helps to be aware of every request with them.

# data[].attributes.body
Thanks to Kal and Matt for testing work that required extensive testing and have a huge volume of test cases to make sure the work is reliable

# data[].attributes.body
Making it through my first rotation in queue. And to all the admins for improved communication about NUSI (no update set incidents). Our process and communication/collaboration continues to improve.

# data[].attributes.body
I have completed all assigned stories and tested some for the queue and helped the team to achieve their sprint goal