You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue 01: Wrong text is shown for the status change.
Steps to reproduce:
Enable the MS calendar plugin
Open the ms calendar settings for Mattermost server via slash command
Then set 'Setting: Get Confirmation' to Yes
Also set 'Setting: Set Custom Status' to Yes
Now schedule a meeting from outlook calendar
Check the text shown for status change message.
Expected: Appropriate and accurate text should be shown. Actual: Wrong text is shown for the status change.
Issue 02: Custom status is not getting updated properly
Steps to reproduce:
Enable the MS calendar plugin
Create two overlapping meeting from outlook calendar like - one from 10:00 am to 10:15 am and second from 10:15 am to 10:30 am
Check the custom status for second meeting
Expected: No delay should be there in updating the custom status of the second meeting Actual: Around 4 min delay is found for the updation of custom status for the second meeting
Suggestion:- The reason behind both of the issues is the time interval for the job which runs to fetch the upcoming events planned in the next defined time interval.
The text was updated successfully, but these errors were encountered:
I found two issue while testing this plugin
Issue 01: Wrong text is shown for the status change.
Steps to reproduce:
Expected: Appropriate and accurate text should be shown.
Actual: Wrong text is shown for the status change.
Issue 02: Custom status is not getting updated properly
Steps to reproduce:
Expected: No delay should be there in updating the custom status of the second meeting
Actual: Around 4 min delay is found for the updation of custom status for the second meeting
Suggestion:- The reason behind both of the issues is the time interval for the job which runs to fetch the upcoming events planned in the next defined time interval.
The text was updated successfully, but these errors were encountered: