Cron description on UI is divergent from cronevaluation endpoint
Description
PRDE - Bug default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
@Breno Zipoli Monteiro Papa
02 - PROBLEM (WHAT'S THE ISSUE?):
The UI page of scheduled tasks show the scheduled times defined by cron expressions wrongfully when comparing with cronevaluation endpoint.
Example:
This schedule will execute not on Tuesday and Friday but on{{ Monday and Thursday.}}
The cron expression on the task is as follows:
"0 0 14 ? * 2,5"
curl 'https://totvstechfin.carol.ai/api/v1/queries/filter?indexType=MASTER&offset=0&pageSize=25&scrollable=false&sortBy=mdmCreated&sortOrder=DESC' \
x -H 'accept: application/json' \
-H 'authorization: xxxxxx' \
-H 'content-type: application/json'The endpoint cronevaluation returns correct dates.
curl -X 'POST' \
'https://totvstechfin.carol.ai/api/v3/tasks/cronevaluation?cronExpression=0%200%2012%20%3F%20*%202%2C5&timeZone=UTC&iterations=5' \
-H 'accept: application/json' \
-H 'Authorization: Bearer 1cf1c253bef5471e8fb1040718eb5ad3' \
-d ''03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
Create a scheduled task using cron and the UI will show divergent schedules from cron expression UI calculation and actual execution.
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):
Activity
Details
Priority
High
This issue was automatically transitioned to DONE after being deployed to production on Github.
https://github.com/totvslabs/carol-ui/releases/tag/v4.37.0
No associated issue on JIRA TOTVS BRAZIL.
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by carlosafw,douglascoimbra.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
fix(schedule): weekdays index should start at 1
Retested and it was FIXED
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
@Robson Thanael Poffo ,
@Geny Isam Hamud Herrera , @Andre Pasold ,
This issue was planned to be delivered until 2023-12-11. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-11-20, 2023-12-11
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
@Robson Thanael Poffo ,
@Andre Pasold ,
This issue was planned to be delivered until 2023-11-20. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2023-11-20
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
fix(schedule): weekdays index should start at 1
This issue was automatically transitioned to IN PROGRESS, as its branch was just created in Github.
CAPL-5031-fix-cron-description-weekdays