...
4. Fill in the mandatory fields that are highlighted red and then save the job.
Cycle Start and End Date Selection Limitations
How vortex works with the project and folder watcher job start and end dates
- Users are able to select the cycle start and end dates as per release start and end date.
- If the project has a start date, no end date, and no release end date, then the user will be able to select the cycle start date using the release start date and the end date will be any date from the release start date.
- The release end date will be considered while selecting the cycle end date if the project has no end date.
Identifying when Vortex is not working due to the cycle start and end dates being out of range
- If the project end date is beyond the current date (Ex: the current date 08/23/2019 and the project start date is 08/01/2019, the end date is 08/20/2019) while configuring a job, the user will receive an error in the UI when trying to click on the save button stating 'Project has completed'.
- If the user selects a future date as the project start date (Ex: the current date 08/23/2019 and the project start date is 08/20/2019, the end date is 08/30/2019) while configuring a job, the user will receive an error in the UI when trying to click on the save button stating 'Project has completed'.
- When executing a folder watcher job with the above errors, the user will get the project is completed error and in the zephyr logs, the logs will contain information regarding the cycle creation failure and the update cycle method will also be logged as failed within the zbot logs.
| Warning |
|---|
When using folder watcher, users will still be able to execute a job irrespective of selecting a project start and end date. The Execution of the folder watcher job will not fail. This is not intended and we advise that you do not attempt to execute a folder watcher job without a start and end date. |
After saving and adding the job, the job will be created with the status set as 'new'.
...