Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can always test your connection to see if it is set up correctly by clicking on "Test Connection” button.

Filtering

Basic/JQL filter

By default if any selected event (see Events section below) takes place in any issue in project - a notification will be immediately sent to Telegram group chat. If you want to limit the number of monitored issues, 2 modes of filtering are available: Basic and Advanced.

 

...

You can switch between filtering modes by clicking on the corresponding toggle. Note that only one filtering mode can exist at a time.

 

...

Label next to the toggle element will give a hint on what filter mode is configured for current setting.

 

Basic

...

Advanced

...

Filter update will take effect immediately after saving settings and will erase another filter mode if configured.

Author

As administrator you can narrow down notification on events depending on who is their author. i.e. Who performed the action from the selected events list (see Events section below).

For example you can set up notifications to be sent only if they are performed by some core users (like managers or team leads) or a specific team. This can be done by defining specific users or via user groups.

Or you can exclude notifications of events performed by specific users simply mentioning them in the field “Exclude users”.

...

Events picking

After managing the Telegram group ID and bot commands users can select events they want to be notified on. Each configuration is split by sections of events depending on their specifics:

  • Comment

  • Issue

  • Worklog

  • Versions

...

  • Sprint

...

Activating toggles next to events will enable sending notifications to Telegram chat as soon as this event takes place in Jira.

...

Expand
titleEvents List

(info) Events will trigger notification only for those issues, that match filter for current configuration. Any event in issues that do not follow the configured filer will be ignored.

 

Event

Description

Comment

Comment added

Event triggers notification when a new comment is left in issue.

Comment edited

Event triggers notification when comment in issue is edited.

Issue

Issue created

Event triggers notification when issue is created in project.

Please note, that event will only work if newly created issue matches the configured filter.

Issue updated

Event triggers notification when issue is edited.

Issue assigned

Event triggers notification when issue assignee is changed.

Issue deleted

Event triggers notification when issue is deleted.

Issue moved to project

Event triggers notification when issue is moved from another project to the current one.

Please note, that event will only work if moved issue matches the configured filter.

Issue moved from project

Event triggers notification when issue is moved from current project to the another one.

Please note, that event will trigger notification regardless of the configured filter!

Issue resolution changed

Event triggers notification when issue resolution is changed.

After event activation a select list will appear. You can select specific resolutions you want to be notified of.

Issue status changed

Event triggers notification when issue status is changed.

After event activation a select list will appear. You can select specific resolutions you want to be notified of.

Worklog

Worklog added

Event triggers notification when time is logged on issue.

Worklog updated

Event triggers notification when logged time on issue is edited.

Worklog deleted

Event triggers notification when logged time on issue is deleted.

Versions

Note, this block of events is not related to configured filter.

i.e. Notification will be sent regardless of the configured filter!

Version created

Event triggers notification when new version is created in project.

Version released

Event triggers notification when project version is marked as "Released".

Version unreleased

Event triggers notification when project version changes its state from "Released" to "Unreleased"

Version updated

Event triggers notification when new changes to project version details are made.

Version merged

Event triggers notification when two project versions are merged into one.

Version archived

Event triggers notification when project version is moved to "Archive".

Version unarchived

Event triggers notification when project version is moved from "Archive".

Version deleted

Event triggers notification when version is deleted from project.

Basic/JQL filter

By default if any selected event (see Events section below) takes place in any issue in project - a notification will be immediately sent to Telegram group chat. If you want to limit the number of monitored issues, 2 modes of filtering are available: Basic and Advanced.

 

...

You can switch between filtering modes by clicking on the corresponding toggle. Note that only one filtering mode can exist at a time.

 

...

Label next to the toggle element will give a hint on what filter mode is configured for current setting.

 

Filter update will take effect immediately after saving settings and will erase another filter mode if configured

Sprint

Sprint Started

Event triggers notification when sprint related to current project was started.

Sprint Completed

Event triggers notification when sprint related to current project was completed.

Extra fields

Each card has its own set of fields, yet for some events you can set up additional fields to display in the cards sent to Telegram group chat.

 

...

 

 

 

You can see an icon next to some events, clicking on which would open a drop down list of fields. Search and select the field which value you want to be displayed in the card sent to Telegram group chat.

 

 

 

 

 

 

After all settings have been set, save them to apply changes. As soon as they are saved, notification will start reaching your channel.

Press Save to apply your changes.

...