Hi David,
We have noticed that if we create this issue via email and filling in the Original Estimate, this issue occurs.
Example, I had sent the following email to create an issue and I was able to reproduce
From: Bagga, Rekha
Sent: Wednesday, August 26, 2009 6:21 PM
To: jiramail
Subject: PHAAS
project: ETP - Atlassian ALM
components:
summary: Test - please ignore
reporter: rbagga
assignee: rbagga
dueDate:
dueDateFormat: dd-MMM-yyyy
priority: 2
issueType: Bug
watchers: rbagga
workEstimate: 8h
fixVersions:
affectsVersions:

So if the above email is sent, and an issue is created for the project mentioned from email
then we will see the issue where in the remaining estimate does not get filled in at all - says Not specified
Please see attachment.
What happens then is that when we log work against this issue, the automatic update of the remaining estimate is not occuring and as a result some metrics data are incorrect.
What needs to happen is, when an issue is created with an original estimate, the remaining estimate has to be equal to the original estimate
Hope this makes sense
Thanks
Rekha
So if the above email is sent, and an issue is created for the project mentioned from email then we will see the issue where in the remaining estimate does not get filled in at all - says Not specified Please see attachment. What happens then is that when we log work against this issue, the automatic update of the remaining estimate is not occuring and as a result some metrics data are incorrect. What needs to happen is, when an issue is created with an original estimate, the remaining estimate has to be equal to the original estimate Hope this makes sense
Thanks Rekha