...
Label next to the toggle element will give a hint on what filter mode is configured for current setting.
Basic
...
Info |
---|
In Basic mode filtering is performed using "AND" operator between field values. Example: |
Filter | Result |
---|---|
If user selected several fields as filter criteria only those issues will trigger notifications that match at least one value for both fields. Selecting several priorities will trigger event notification in issues with both "Medium" and "High" priority. | |
Issue with "High" priority in status "Open" will trigger notification. Issue with "High" priority in status “Closed" will not trigger notification. |
Advanced
...
Filter update will take effect immediately after saving settings and will erase another filter mode if configured.
...
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
|
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.
...
Select Report Type
Configure issue filter
Set up the schedule
I. Report type
Report type | Description |
---|---|
Custom sprint | Sends report on issues in the selected Sprint(s). |
Active sprint | Provides reports on issues in currently active Sprint(s). |
Issue count | Lists issues matching the selected filter. |
Progress | Shows aggregated progress state of issues in filter. |
No transitions | Lists issues that have status not changed. (Based on Minimum overdue) |
No updates | Lists issues that have not been updated. (Based on Minimum overdue) |
Info |
---|
Some reports require filling extra field to make this report work. For example "Custom Sprint" report requires selecting the specific Sprint related to current project while "No transitions” and "No updates” reports demand setting a "Minimum overdue”. Minimum overdue - is the time delay since last event occurrence and current time. If selected report events happened before the minimum overdue period, it will be included into report. |
...
Each period has a different set of fields that help to adjust the correct time for sending report. You can see the fields corresponding to each of the periods below:
Period | Hour | Minute | Day of week | Mode | Day of month |
---|---|---|---|---|---|
Daily |
|
|
| ||
Weekly |
|
| |||
Monthly |
| First day of the month |
| ||
Last day of the month |
| ||||
Custom day of the month | |||||
Once in | This type of period has a unique set of fields and logics behind it: |
While period types like Daily, Weekly and Monthly send reports only once in a specified day and time, the "Once in" type lets you get reports more frequently and within a range of days and time.
...