Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: timetracking field always marshalled #768

Closed
wants to merge 1 commit into from
Closed

fix: timetracking field always marshalled #768

wants to merge 1 commit into from

Commits on Aug 27, 2024

  1. fix: timetracking field always marshalled 

    Currently, the field for timetracking is always marshalled to JSON even if the "OriginalEstimate" field is an empty string.

This is because of the way the field is initialized as a struct that will never be nil and therefore never caught by the 'omitempty' tag.

This changes the TimeTracking field to be a pointer, which is nil by default, so that if OriginalEstimate isn't set, the timetracking field won't be in the JSON sent to Jira.

This is a problem if the issue type being created is one that doesn't support a timetracking field.
    @wbh1
    wbh1 committed Aug 27, 2024
    Configuration menu
    Copy the full SHA
    af4df2d View commit details
    Browse the repository at this point in the history