Weekly Sprint Reports Delivered to Telegram
Every Friday, a comprehensive sprint report lands in Telegram. Closed issues, velocity, blockers, metrics. Your retro prep is already done.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Document
Send general files (documents) to a telegram chat using the bot api.
Why this helps
Sprint retros require digging through Jira to gather data. You waste meeting time collecting information instead of discussing improvements.
- Retro prep is automated
- Metrics always available
- Historical sprint data
- Faster decision-making
Setup
Build it in a few focused steps.
- 1Connect Jira and Telegram to Notis via the portal.
- 2Create an automation: 'Every Friday at 4 PM, send a document to #retros with this sprint's closed issues, velocity, and blockers.'
- 3Select the 'Weekly Schedule' trigger and your retro channel.
- 4Verify by checking the first report arrives with complete sprint data.
Questions about this workflow
What metrics are included?
Issues closed, velocity, blockers encountered, team capacity, and unfinished work. You can customize which metrics matter.
Can I compare weeks or quarters?
Yes. Your prompt can request trend data: 'Compare this week's velocity to the last 4 weeks and flag trends.'
How is velocity calculated?
Notis uses your Jira story points or issue count. You define the metric in your automation prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Telegram. A trigger fires from one place; an action lands in another.
Jira triggers
Telegram actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
New Project
Triggered when a new project is added in Jira
Delete Message
Delete a message, including service messages, with certain limitations.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Edit Message
Edit text messages sent by the bot.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Not just Jira and Telegram. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Telegram.