The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Jira Premium: Blocked by ticket in other plan is ignored by auto-schedule function
daniel_miesling
October 19, 2020 edited
Issue A is blocked by Issue B (Issue B isn’t planed in Sprint, Release, and hasn't a Due Date).
The plan contains only Issue A.
When using the "Auto-schedule"- function it is ignored that Issue A is blocked by Issue B.
Question: Must all blocking tickets be in the plan to run an "auto-schedule"-function that recognizing all blockers?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
DEPLOYMENT TYPE
CLOUDPRODUCT PLAN
STANDARDPERMISSIONS LEVEL
Product AdminCommunity showcase
Atlassian Community Events
Copyright © 2026 Atlassian