Clean Up Resolved Issues from Telegram
When an issue is marked done or closed, its Telegram message gets deleted. Your channels stay focused on active work, not historical record-keeping.
Trigger
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.
Action
Delete Message
Delete a message, including service messages, with certain limitations.
Why this helps
Resolved issues clutter your Telegram channel. You scroll past hundreds of old notifications looking for what's actually in progress.
- Cleaner channels
- Better signal-to-noise
- Focus on active work
- Reduced scrolling overhead
Setup
Build it in a few focused steps.
- 1Connect Jira and Telegram to Notis via the portal.
- 2Create an automation: 'When an issue is marked Closed or Done in Jira, delete the related message from Telegram.'
- 3Select Jira's 'Updated Issue' trigger (status changes) and your team channel.
- 4Test by closing an issue and verifying its Telegram message is removed.
Questions about this workflow
What if I need a record of closed issues?
Deletion only affects Telegram display. Notis and Jira keep full history. You can export or archive if needed.
Can I archive messages instead of deleting?
Currently, Telegram deletion is permanent. Future versions may support moving messages to an archive channel.
Does this apply to all statuses or just Done?
You define the statuses in your prompt: 'Delete when status changes to Closed, Done, or Won't Fix.'
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.