Back to projects

Digidel

User stories in sprints on an app that tracks the hours of staff representatives.

Context
Summer 2026 at AREA (APRR group)
Period
July – August 2026
Role
Apprentice in a Scrum team
Team
Scrum team
  • Java
  • Spring Boot
  • Vue.js
  • Vuetify
  • JPA
  • Flyway
  • Azure DevOps

Context

Staff representatives have hours for their mandates. Digidel keeps track of these hours and of the delegation slips they fill in. During the summer I joined the team and took user stories from the backlog. Each one went through a pull request on Azure DevOps.

Linking the situation and the planning

On the home page the situation and the planning each had their own month list. Nothing linked them. You could see February 2026 on one side and December 2021 on the other. Now in monthly mode changing one month also changes the other.

Before: the situation shows February 2026 and the planning is still on December 2021After: the situation and the planning both show September 2026
Before and after the change.

Sorting the periods

Users wanted the latest months at the top of the lists. The back end already sorted them that way. I followed the data in the front end and found a second sort run just after login. It put the oldest months first. I reversed it and every list in the app was fixed.

List of periods with the latest month first

Other user stories

  • When you add a mandate the end date is now filled in from the active mandate. I added the API endpoint for it.
  • The e-mail and the UPN (the Windows login) are now two separate fields. The UPN must be unique but several people can share the same e-mail.
  • I created the table that will receive employees from the HR tool, with its JPA entity.
Add a mandate window with the end date already filled in
User form with separate e-mail and UPN fields
User form with separate e-mail and UPN fields. The data shown is made up.