Share Issue Locations with Your Distributed Team
When an issue is tagged with a location (office, city, region), Notis sends a Telegram location pin. Distributed teams instantly know where the issue lives and who owns it.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Send Location
Send point on the map location to a telegram chat using the bot api.
Why this helps
Distributed teams struggle to coordinate when issues are location-specific. Someone in the wrong timezone or region doesn't realize an issue affects their area.
- Clear geographic context
- Distributed team awareness
- Faster regional routing
- Better timezone coordination
Setup
Build it in a few focused steps.
- 1Connect Jira and Telegram to Notis via the portal.
- 2Create an automation: 'When a new issue is tagged with a location (office, city, region), send the location pin to the relevant regional Telegram channel.'
- 3Select Jira's 'New Issue' trigger and your regional channels.
- 4Test by creating an issue with a location tag.
Questions about this workflow
How does Notis extract location data?
From Jira labels, custom fields, or issue descriptions. You describe how location is marked in your prompt: 'Issues with the label [office] send a pin for that office.'
Can I map offices to Telegram channels?
Yes. Your prompt can route issues: 'Send to #london when the office label is London, to #tokyo for Tokyo, etc.'
What if location is mentioned but no official field exists?
Notis can extract location from issue text if you describe it: 'Extract the location mentioned in the description and send to the relevant regional team.'
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.