How to change story points to hours in JIRA

Hemalatha Gopalakrishnan

I have a scenario in my team, where members have a small activity Example: Documentation. adhoc-support, on-call support. These activities might not take more than 30 mins to 2 hours. I have configured SP as the measurement and follow Fibonacci series mechanism of 1SP = 4 hrs. 

Now to track all the activities and also adhere to the SP, I asked team to create TASKS instead of story and create sub tasks and provide SP to the parent task. Now, the trick of what if a particular sub task is in complete, we need to carry the entire TASK To the next sprint (I think so) but for my management they are worried about the reports. 

So I am thinking of option whether we can change the estimating mechanism as HOURS instead of SP during the in progress stage of project execution OR can it be done only for the issue type TASK alone.

What could be the possible pros and cons of this change? 

Thanks

Nic Brough -Adaptavist-

You can't just change the measurement technique part way through a process, it makes a nonsense of your measurement.

You need to decide what you are going to estimate in, and stick to it.  Select story points or the time estimates or another numeric thing, set it in the board configuration and work with it.  Note that "1 story point = 4 hours" defeats the purpose of using story points, you might as well just use the time estimates directly.

As for sub-tasks moving between sprints, they technically don't, individually.  The story they are in is what you're estimating on, committing to and hence the thing that goes into a sprint.  If sub-task is not done within a sprint, then, by definition, its story cannot be complete, so the story goes into the next sprint.  And hence all its subtasks go into the sprint complete or not.

The main con of changing estimation methods during a process is that your current numbers become useless and you might as well throw away all your estimates and reporting.  I can't think of a single pro for it.