Table of Contents |
---|
General Info
...
Even though “Channel" block is not marked out, it contains the basic fields for settings creation:
Title* - is the field containing the name of the setting. Value is also used as setting tab header.
Webhook URL* - field for the link to MS Teams channel.
...
Info |
---|
Link must be retrieved from “Incoming Webhook” connector in MS Teams. Link cannot be used in several settings of the same project. |
* - field marked as mandatory
...
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 MS Teams channel.
...
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 not be included into report. |
You can select report’s owner. Each report must have an owner as his/her permissions will be counted while building report. i.e. if report owner has no permission to view the issue it will not be included into the 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.
...