Issue Summary:

When using hours/days as estimation the allocated Sprint Capacity is decreasing as we log work on issues. This is a different behaviour from using Story Points

Steps to reproduce:

Replication steps are mentioned on the screen recording attached

Expectation :

 The allocated Sprint Capacity should not decrease as the Sprint progresses when using estimate(d/hrs)

Actual Result:

The behaviour here is intended behaviour with the known trade-off that the sprint allocation will appear to reduce as time is logged. It's important that we use the remaining estimate because it's most relevant to the future planning of the remaining work.e.g consider an issue that was originally 8hrs, and had 4 hrs logged in a past sprint. When planning the remainder of that work into a future sprint it's essential to plan it in the context of the remaining estimate (4hrs) rather than the total original estimate (8hrs). Our solutions are generally optimised for Future planning over in-flight tracking so this was the preferred trade-off.