Most frequent causes of Scheduled Issues execution failures

Cause: Some field has not been filled that is now required

Solution: From action column in scheduled issues table click edit and fill required field with value.

Cause: It’s mostly caused in JSM projects - if you using request type field in Scheduled Issue, Scheduler due to limitation must create work item/issue in 2 steps. That’s require access to field that you want to set up in Create and Edit screens. Read more about it below…

Solution: https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/3154378763/Request+type+field#Create%2FEdit-issue-screen

Cause: Scheduler cannot find active sprint in your project

Solution: Go to Board page and check if at least one sprint is currently active

Cause: Scheduler Active sprint option for sprint field support only single active sprint. If you have enabled Parallel sprints for company-managed projects option in Jira and in your project more then one sprint is active then Scheduler will fail to execute Scheduled Issue.

Solution: If you want to use multiple sprints and want to dynamically set active sprint for Scheduled Issue you can use Pattern option - more information here https://psc-software.atlassian.net/wiki/x/AQAc6g

Cause: This error occurs if you previously created Scheduled Issue with child (in manage subtask) and your SI have work type e.g. Task (work type hierarchy 0) and for child e.g. Sub-task (work type hierarchy -1) but then you change SI work type to e.g Epic (which have work type hierarchy 1) but forget to change work type for SI child (in manage subtasks)

Solution: Go to manage subtasks in that Scheduled Issue that have incomplete status. Find which sub-task cause error. After click you should see:

You should change work type for that sub-task.

Cause: Previously created sub-tasks for Scheduled Issues does not contain value for fields that are now mark as required.

Solution: Go to Manage subtasks and fill required field with value

Cause: Issue/Work Item selected in Linked Issues field in Scheduled Issue has been probably removed or it has restrictions.

Solution: Check if that work item has restrictions applied to specified roles or if it’s still exist. You can go also and edit Scheduled Issue, next to Linked Issues field you should see banner with information - and you can reset field value

Cause: Transition selected in Scheduled Issue in field Post create transition does not exist

Solution: Click Edit from actions column for Scheduled Issue and change value for Post create transition field. Workflow for your project can be found in Project Settings → Work Types → Edit workflow

Cause: The Scheduler app doesn’t have permission Link Issues

Solution: Add atlassian-addons-project-access role to your project