Yesterday, ready to paste.

Sprintalyze collects your commits, merge requests, Jira tickets and Teams meetings on one timeline, then writes your morning stand-up from it.

Download Sprintalyze See how it works

Reads GitHub, GitLab, Jira andMicrosoft Teams. Runs on your computer, for Windows.

Friday, 9 October 20269 events

A day of activity collected by Sprintalyze
Time	Tool	Action	Description	Ticket
09:00	teams	meeting	Daily Webapp→ 09:15
09:32	jira	transition	PSWS-1774: Background polling of active copydown operationsTo Do → In Progress	PSWS-1774 Background polling of active copydown operations
10:05	gitlab	push ×3	feat(Copydown): PSWS-1774 Background polling of active copydown ope...3 pushes · 4 commits · on PSWS-1774	PSWS-1774 Background polling of active copydown operations
11:20	gitlab	mr opened	!36 feat(Copydown): PSWS-1774 Background polling of active copydown operationsgrp/backoffice	PSWS-1774 Background polling of active copydown operations
11:30	teams	meeting	Sprint planning→ 12:30
14:02	gitlab	comment	!226 feat(partner): PSWS-1788 add the partner create actionDue date in the past?	PSWS-1788 Create a partner Action
14:10	gitlab	review	!226 feat(partner): PSWS-1788 add the partner create actionchanges_requested	PSWS-1788 Create a partner Action
15:22	jira	comment	PSWS-1705: Banners text limitPSWS	PSWS-1705 Banners text limit
16:40	gitlab	mr merged	!36 feat(Copydown): PSWS-1774 Background polling of active copydown operationsgrp/backoffice	PSWS-1774 Background polling of active copydown operations

Stand-up

Vendredi 9 octobre

Copydown · PSWS-1774 Background polling of active copydown operations : démarré, 4 commits, MR !36 ouverte et mergée
Code Reviews · PSWS-1788 Create a partner Action : changements demandés (1 commentaire)
PSWS-1705 Banners text limit : 1 commentaire
Réunions : Sprint planning (1h)

À faire

PSWS-1777 Copydown permissions : In Progress, MR !38 en review
PSWS-1790 MR !241 Export of the partner list : review à faire (Val S.)

Blocages

PSWS-1896 MR !232 Deadlock on user sync : pipeline en échec

Every line comes from something you did

No AI guessing and no template to fill: the stand-up is computed from your events, with the noise left out. Read it over, then paste it.


                Vendredi 9 octobre :
                
            
                - Copydown · PSWS-1774 Background polling of active copydown operations : démarré, 4 commits, MR !36 ouverte et mergée, livré en 3.12.11
                ¹
            
                Change Logs
                ²
            
                - Mise à jour de 3 tickets (description) « Implement activity logs for … » : imports, pages, widgets
                
            
                - PSWS-1286 Implement activity logs for entity forms : passé en Testing On QA
                
            
                - Code Reviews · PSWS-1788 Create a partner Action : changements demandés (4 commentaires)
                ³
            
                - Réunions : Sprint planning (1h), Call client (30 min) — point sur la migration
                ⁴
            
                À faire :
                
            
                - PSWS-1777 Copydown permissions : In Progress, MR !38 en review
                ⁵
            
                - PSWS-1790 MR !241 Export of the partner list : review à faire (Val S.)
                ⁵
            
                Blocages :
                
            
                - PSWS-1896 MR !232 Deadlock on user sync : pipeline en échec, rebase nécessaire
                ⁶

One line per ticket, saying how it moved that day: the Jira transition, the commits of three pushes, the merge request and the release tag. Merge commits, deleted branches and rebases are left out.
Lines are grouped by topic, the scope of your commit messages. Tickets without code borrow the topic of look-alike tickets. Tickets you only edited, or only created, become one line.
Other people's merge requests that you reviewed are kept apart, with your verdict and how many comments you left.
Teams meetings from your calendar, except the daily itself, with their length. Calls nobody scheduled can be added by hand.
What is open right now: your Jira tickets in progress with their merge request, and the reviews other people are waiting for.
Merge requests in trouble: failed pipeline, changes requested, conflicts, unresolved discussions, or no approval after two working days. Blocked tickets too.

The whole day on one page

Every tool on one timeline

Commits, pushes, merge requests, reviews, Jira changes and meetings, in the order they happened. A run of pushes to one branch becomes one row, and rows about the same ticket share a color.

Keep what matters

Tick the rows worth mentioning, switch to Highlighted only, and the stand-up covers those rows alone.

Add what no tool saw

An unplanned call, a hand-written note. They sit in the timeline with the rest, and a ticket key in the text links them to the ticket.

Your month in three numbers

Merge requests opened, merged and reviewed this month. Point at a number to see the merge requests behind it.

Set it up once, then just open it

Connect your accounts
In Settings, paste a GitHub token, a GitLab token, a Jira API token and the link of your published Outlook calendar. Test each one before saving.
Let it collect
While the app is open, it fetches what is new every hour. Fetch a day or a range on demand, or backfill past months in one go.
Copy the stand-up
In the morning it opens on the last day you worked: Friday on a Monday, the day before your leave when you come back. Read it, copy it, paste it.

Your activity stays on your computer

Sprintalyze is a desktop app, not a web service. Your events, ticket titles and tokens are kept in a database file in your user profile.
It only talks to the services you set up: your GitHub, your GitLab, your Jira, your Outlook calendar.
There is no account to create, no server of ours in between, and no analytics.

Read the privacy policy

Questions

Does it see what my teammates do?

No. It reads your own GitHub and GitLab activity, and in Jira only the changes and comments you made on tickets you are assigned to, reported, created or watch.

My admin won't let me register an Azure app. Can I still get my Teams meetings?

Yes. Publish your Outlook calendar (Outlook on the web, Settings, Calendar, Shared calendars) and paste its ICS link in Sprintalyze. Signing in through Microsoft Graph is an alternative with fresher data, not a requirement.

Do I need all four tools?

No. Set up the ones you use; the others are skipped.

How far back can it go?

Commits on default branches: as far as GitHub search goes. GitHub pull requests, reviews and pushes: about 90 days, which is all GitHub keeps. GitLab: what your instance keeps. Teams meetings from the ICS link: about a year.

Which language is the stand-up written in?

French: Hier, À faire, Blocages, ready to paste for a French-speaking team. The app itself is in English.

Does the app have to stay open?

Only for the hourly collection. When you open it after a while, it catches up from where it stopped.

Try it on tomorrow's stand-up.

Download Sprintalyze

For Windows. Version 2.0.0.