Skip to content

Jira 3.5 Issue. User will never match #66

@jerrycheng9

Description

@jerrycheng9

As Jira is updating from 2.0.0.sg.3 to 3.5. It seems has dropped equal function for Jira.resources.User class.
Here is Jira-2.0.0 Version
image

And here is Jira-3.5.0 Version
image

Thus the direct equal function for comparing two jira user which has Jira.resources.User which not return the desired result. And changing assignee will not be able to sync to Jira properly.

For example, the following code will never proceed since it is comaping two calss instance.
https://github.com/shotgunsoftware/sg-jira-bridge/blob/master/sg_jira/handlers/entity_issue_handler.py#L436C21-L436C21

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions