Story-Point Estimates along side Time Tracking

[MatBailie]

I've read various questions and answers and I'm really struggling to setup up a Project/Sprint/Story/SubTask to get what we think we need.

In terms of long term planning I've sold my team on the idea of Stories, estimates in Story Points, then measuring Velocity in Story Points.

The stories, however, can easily be quite big; taking a week or more to complete.  This is because a lot of the work is essentially "Research something, then document document it and output some options and recommendations (with relative merits, etc)".  That nicely fits with a break-down in to various sub-tasks; different topics to research being separate tasks, documentation of each topic being separate sub-tasks, final options and recommendations being another sub-task.

Where we're becoming unstuck is that a burn-down chart in story points is next to useless for us.  We see nothing happen for a week or more, then suddenly a massive percentage of the work is completed.  So, we read about using Story Points for estimation and then adding time-tracking.  https://confluence.atlassian.com/agile067/jira-agile-user-s-guide/configuring-a-board/configuring-estimation-and-tracking

As far as we understand it, and we may be wrong, we want the following process:

• Add a Story to the back-log, with a Story Point estimate
• When we move that Story in to a Sprint, then create sub-tasks and estimate them in days/hours (but don't change the Story's Story Point estimate)
• As we work the Sprint, log changes to Estimated Time Remaining on each Sub-Task
• Use a Burn-Down chart to track progress, the target being 0 hours remaining by the end of the sprint?
• Use Velocity based on Story Points to estimate capacity for future sprints

So far we have the Stories estimated in Story Points, and the configuration below for Time Tracking.

But we can't figure out how to set an Initial Time Estimate of the Sub-Tasks...

  

[Derek Fields _RightStar_]

You don't need to break the stories into sub-tasks unless you want to do that. Story Ponts are entered through your Sprint board, generally during Sprint Planning or Backlog Grooming. When you are ready, you put an Original Estimate into the Story and then use Worklogs to deduct from the Original Estimate. You need to turn on Time Tracking for this work (which you probably already have). Make sure that Time Tracking is added to the screens for the Story Issue Type. 

[Lindsey George]

Is there a way to automate the conversion of story points to original estimate? 

[MahendraH]

Did you mean converting the story points to number of hours? If yes, then the point itself is not valid. Story point is different the sum of the hours of the subtasks is different. There is no relationship between story points and hours.