Portfolio users who have their plan based off an issue source that is a board or filter may not get a scheduling result and thus see nothing in their timeline.
      This occurs for issue sources that go beyond the basic query usually associated with a board (which is its associated project query). From our current investigations, it seems like queries that are more complex than

      • project in (<projectKey1>, ..., <projectKey n>) ORDER BY rank
      • project = <projectKey> ORDER BY rank 

      result in this problem. That is 

      • project = <projectKey> AND (issuetype is Epic) ORDER BY rank 

      would not yield a scheduling result, the same goes for

      • issuetype in (Story, Task, Epic) ORDER BY rank ASC

      or the like.

      We are aware of the severity of this problem and are working on it with highest priority. A fix is already in the making.

            [JRACLOUD-88383] No scheduling result for plans based on certain JQLs

            There are no comments yet on this issue.

              Unassigned Unassigned
              dannesley Daniel (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: