Remaining estimate is always showing 0 instead of burning down from Original estimate.

[Teal Nissley]

We pull the original estimate in from an outside system. The remaining field is not using the original estimate, instead it is always showing 0.

[Abdoulaye Kindy Diallo · Accepted solution]

Teal, 

It appears that this is a known issue with the Salesforce plugin. Basically, the Remaining Time field will only be reflected if you update the field through the UI. Once you edit the issue and click on the "Update" button, you should see the remaining time. 

[Nic Brough -Adaptavist-]

When you say you "pull the original estimate from an outside system", what does that mean?  How are you doing that and where is it going?  What does it look like when you visit the issue in Jira?

[Teal Nissley]

We have a connector to Salesforce and we are pulling over a field so we can see how many hours were budgeted for the project. This is working correctly.

The remaining estimate field is showing as 'Not Specified' when looking directly at the issue and 0 hours when looking at the card on the board.

[Nic Brough -Adaptavist-]

But what does "pulling over a field" mean? Where is it going? What does it look like when you visit the issue in Jira?

[Teal Nissley]

See below. The original estimate field is getting the correct value, but the remaining estimate is not.

[Nic Brough -Adaptavist-]

But what does "pulling over a field" mean? Where is it going? What does it look like when you visit the issue in Jira?

[Teal Nissley]

We have mapped a field in SFDC to the Original Estimate field in JIRA. We use a product by Service Rocket that connects JIRA to SFDC. The value is being mapped correctly, but the remaining estimate is not populating based off of Original Estimate.