fix(jira): display originalEstimate field in issue view#1797
Open
LivingTheCoderDream wants to merge 1 commit into
Open
fix(jira): display originalEstimate field in issue view#1797LivingTheCoderDream wants to merge 1 commit into
LivingTheCoderDream wants to merge 1 commit into
Conversation
The Original Estimate field was present in Jira but not rendered in the issue detail view.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Original Estimate field is set in Jira but is completely absent
from the issue view in the extension, making it impossible to see
time estimates without leaving the IDE.
Solution
Render
originalEstimatein the issue detail view when the valueis present.
Changes
src/path/to/component.tsx: 3 lines added to conditionally render originalEstimateScreenshots
BEFORE:
AFTER:
Rovo Dev code review: Rovo Dev couldn't review this pull request
The pull request author does not have access to Rovo Dev.