You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
It is not required to use both. However when using portfolio, I would probably be more inclined to use the original estimate field when the issue has no estimates at all yet. This can be useful later on when this issue is then seen by your teams working those issues. Those team members might adjust the estimate on the issue, or log work against it. However the original estimate is not expected to change once the issue has started logging work against it, or it exists in an active sprint. But by using the original estimate field, you can then compare against the other estimate field to see how close you were.
I hope this helps, but in case it does not, perhaps check out this recent blog post about using estimates for Portfolio: Estimation best practices with Portfolio for Jira