...
There are 3 main blocks in any configuration tab:
Webhook URL
Filter
Events
Channel
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. 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. | Mentioned users | Event triggers notification when an "@-mention" is used in issue comment. | 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. | 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. |
|
Event notifications can work in 2 modes:
Instant
Batch
In Instant mode, notifications are sent to channel the same moment event takes place in Jira. While in Batch mode notifications are stacked until the set up schedule condition is met. Once the time is up, notifications are sent in an organised manner.
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.
...
To to set up a report project administrator must take 3 simple steps:
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) |
...