Stages scheduled concurrently rather than sequentially

SYSTEM:

JIRA portfolio version: 1.9.2
JIRA version: 6.3.15

SCENARIO:

• Our "definition of done" is typical. Both implementation and testing must occur for a story to be complete.
• Although there is some back-and-forth, the bulk of those two activities occur in two distinct, sequential stages.
• We want most stories to be completed in a single sprint.
• As suggested by "Understanding Stages and Skills" at https://confluence.atlassian.com/pages/viewpage.action?pageId=715262985, we are using stages for sequential activities.

>"Typically, stages are used for activities that need to be done sequentially per work item."
>...
>"Another likely setup could be:
>"* Design
>"* Implementation
>"* Test"

• In "Configure stages and skills," I've created two stages: "Development" and "QA."
• On the "People" page, I've created a team with two people, one checked for each stage.
• On the "Backlog" page, I've created a single story, assigned to that team.
• To allow both stages to be scheduled within a single sprint, I've turned off the "stage/sprint constraints" in the plan configuration accessed via "Plan>Configure," on the page accessed with "Planning>Scheduling."
• I've configured the schedule views at the bottom so that "Grouping" is by "Members."
• I've examined the Epics, Stories and Capacity views.

EXPECTED:

• The QA stage will occur, and should be scheduled, after the development stage.

OBSERVED:

• The QA and development stages are displayed as concurrent, at least in the Epics, Stories and Capacity views.