How sub-tasks are not always ideal. Example:
"https://answers.atlassian.com/questions/108172/planning-sprint-in-greenhopper-6-with-scrum-board-no-subtasks-shown".

1) Not everyone's workflow matches your ideal, JIRA is really powerful and should allow us to hang ourselves if we want to.

We should be able to estimate points on subtasks and have those points roll up to their parent stories. This should be our teams choice if we want to configure JIRA this way, not yours.

At the very least the plan view should show subtasks without having to click on a story. I'm ok with the sub-tasks following the parent story when you move it, but having the sub-tasks show is very important for our team's work flow and how we estimate the parents stories work. The current implementation leaves a lot to be desired.