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

Bugzilla Parser only fully works for issues but not for issues comments #299

Open
anthonyjlau opened this issue Apr 27, 2024 · 2 comments
Open

Comments

@anthonyjlau
Copy link
Collaborator

anthonyjlau commented Apr 27, 2024

The Bugzilla parser is able to parse issues and issues with comments for the Red Hat Bugzilla website. However, it is unable to parse issues with comments for other Bugzilla websites. The reason for this is because the comments field of the Red Hat json file is slightly different from the format of other websites. For example, this Red Hat API call is different from this Mozilla API call. For this case, the Red Hat json file has a field called 'creator_id' while the Mozilla json file does not have that.

Another problem is that some websites do not provide comments even when the include_fields parameter has comments. For example, this GCC API call (https://gcc.gnu.org/bugzilla/rest.cgi/bug?creation_time=2024-04-25T00:00:00Z&include_fields=_default,comments&limit=20&offset=0) has include_fields=_default,comments, which means it should include details about the comments on the bug. However, there is no comments section at all.

@anthonyjlau anthonyjlau changed the title Bugzilla Parser only works for issues but not for issues comments Bugzilla Parser only fully works for issues but not for issues comments Apr 27, 2024
@carlosparadis
Copy link
Member

@anthonyjlau Could you post a few screenshots here of the sections with the difference? I.e. without comments, create_id, and also the offset portion you showed on call?

@anthonyjlau
Copy link
Collaborator Author

image
This is what the comments fields look like for the Red Hat API call.

image
This is what the comments fields looks like for the Mozilla API call.

The offset part is more relevant in issue #300 which I mentioned in there.

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