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.

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

Jira 3.5 Issue. User will never match #66

Open
jerrycheng9 opened this issue Aug 2, 2023 · 1 comment
Open

Jira 3.5 Issue. User will never match #66

jerrycheng9 opened this issue Aug 2, 2023 · 1 comment

Comments

@jerrycheng9
Copy link

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

@jerrycheng9 jerrycheng9 changed the title Jira 3.5 Issue Jira 3.5 Issue. User will never match Aug 2, 2023
@carlos-villavicencio-adsk
Copy link
Contributor

Hello, have you tested this and confirmed the issue? It seems the equal function has moved to the parent Resource class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants