Can Enforcement of Velocity Based Scheduling be Disabled in Portfolio?

[Matan Levin]

Background:

Our backlog is ordered by rank, with the most important stories at the top. We are in the process of evaluating JIRA Portfolio, and we noticed a behavior where in the process of auto-scheduling, Portfolio will skip certain higher ranked items in the backlog and instead pull in lower ranked items, situated further down in the backlog - all with the objective of sticking to the team's velocity. 

Here is an example:

My team has a velocity of 11.  Ticket 1, which is at the top of the backlog and ranked the highest has 8 points. Ticket 2, which follows, has 8 points as well. Given the total for these two tickets is already 16, Portfolio only scheduled Ticket 1 for the next sprint, and then skipped down the backlog till it found Ticket X which is estimated at 3 points and then pulled it in so the total would be 11 points per sprint which is the team's velocity. 

While this is a good way of representing what is feasible from a velocity perspective, it doesn't reflect the actual ranking of the items in the JIRA backlog. 

My question is:

Is there a way to disable this behavior? Instead, can Portfolio simply schedule based on the ranking in the backlog and just flag items that overflow the sprint? 

Thanks in advance,
Matan