Watch our demo video for a brief introduction
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Note |
|---|
Incompatibility with the IP restriction feature Currently our app cannot work if you have the IP restriction feature active. Monday is working on a solution for this problem. In the meantime, you will have to disable the IP restriction feature. You can find more information here: |
Using SLA, you can define various SLAs and their goals, which are essential for managing and measuring the performance and quality of service provided to customers or colleagues.
...
Standard, Important, Critical
Standard, Advanced, Premium
Gold, Silver, Bronze
Basic, Intermediate, Advanced
Level 1, Level 2, Level 3
The first two goal names collections are used in the initial configurations (Click here for more details: How to initialize SLAs ). You can freely create your own configurations (Click here for more details: How to define SLAs and their goals ).
...
Based on this information, an SLA goal instance (hereinafter also referred to as an ongoing SLA or simply SLA) is created.
Ongoing SLA states
It can have the following ongoing SLA states:
running – a running SLA has a due date
paused – a paused SLA has a remaining runtime
stopped – a stopped SLA can have a met or missed due date
SLA transitions
The following state transitions exist:
Start/Create – starts an SLA, calculates the due date, and sets it to the running state
Pause – pauses a running SLA, the remaining runtime duration is calculated, and the state is then paused
Resume – restarts a paused SLA, based on the remaining runtime duration the due date is calculated, and the state is then running
Stop – ends an SLA, it is determined whether the due date was met, and the state is then stopped
Restart – starts an SLA, calculates the due date, and sets it to the running state.
There are a number of integrations for board automation (Click here for more details: How to use our Core integrations within Board automation )