You may wish your Spring Boot application to run with a timezone different from your machine's default. In this tutorial, you can learn to configure this at different points during Spring's startup.

Baeldung offers insights into Java development, Spring framework, and software architecture, providing tutorials, articles, and best practices for mastering Java programming language and its ecosystem. By exploring Baeldung's curated content, developers can learn about Spring Boot, Hibernate, RESTful APIs, and microservices architecture for building robust and scalable Java applications. Whether you're a Java beginner or an experienced developer, Baeldung offers resources to deepen your understanding of Java development and stay updated with industry best practices.

Baeldung

Learn different ways to set the default TimeZone in a Spring Boot Application, including using JVM arguments and programmatically at startup.

Setting Default TimeZone in Spring Boot Application

3. Setting Default TimeZone on bootRun Task

4. Setting Default TimeZone on JAR Execution

5. Setting Default TimeZone on Spring Boot Startup

Uncertainty is another factor to consider when using story points. You can have an probably easy change that comes with some doubts, problems that may arise. The senior the team the more they recognize this and can assign better points the story.
As an example: an story to update dependencies on a project that is not too far behind the newest dependency releases. But how can you be sure there is nothing incompatible? The dev may face unknown problems, may have to discuss with the team if they should abort or update partially, etc.
Of course, when estimating feature for a customer, we use metrics converting to hours, or even better, days/sprints (very aproximated ofc) to give a rough estimation, but one that tends to be very good.