"dataquality/dataplatform" not working as expected

[bsieber-mozilla]

Slack message: https://mozilla.slack.com/archives/C016BTJKM9B/p1682060585086999

[sentry-io[bot]]

Sentry issue: JIRA-BUGZILLA-INTEGRATION-45

(@bsieber-mozilla linked this)

[bsieber-mozilla]

~I believe there is some issue with the way we are passing jira_components in production?~

---

I tried to reproduce this issue in staging (adding the components in question to the JB project) but it was able to process in staging: https://bugzilla-dev.allizom.org/show_bug.cgi?id=1633577

[scholtzan]

Hey, just wondering if there has been any update on this issue?

[bsieber-mozilla]

Hey Anna, just reached out on Slack--moving the comment here:

Hey Anna, it seems debugging this has taken awhile thus far--I believe this has to do with either the components having differing access levels than the main project (and the service account doesnt have permissions) or the status’s aren’t mapping. (Is that something you can confirm/ provide a What I suggest for now, to get this data flowing--we remove the component mapping; the “Components” and routing/adding this data can still be added. @Julien could inform you a bit about how Jira Automation fills in some of the edges for this sync system.

Thanks for your patience as we debug this issue. What are your thoughts on Jira Automation to apply the components label at this time?

[bsieber-mozilla]

In the above comments, I point out how this problem is not reproducible in stage--I've opened a JSM request to ensure that the Service Account has the right permissions for production.

remove components PR: https://github.com/mozilla/jira-bugzilla-integration/pull/489/files JSM access ticket: https://mozilla-hub.atlassian.net/servicedesk/customer/portal/4/SDD-14054?created=true

[grahamalama]

@scholtzan, following up on this:

We enabled some new logging in #503, and we're seeing a possible source of this issue:

"labels": "Field 'labels' cannot be set. It is not on the appropriate screen, or unknown." Source: https://mozilla.sentry.io/issues/3571741650/?project=6364263

For now, we're going to disable the sync_whiteboard_labels feature (docs) to hopefully unblock the queue. This means that the whiteboard tags on the bug won't be added as labels on the issue.

We think the error message that Jira is responding with means that there isn't an option to add labels on the "new issue" screen of the DENG project. If you'd like to reenable this feature, we'll want to make sure that field is there. @jchaupitre, what are your thoughts about our hunch of the issues field missing?

[scholtzan]

Would it make sense to revert https://github.com/mozilla/jira-bugzilla-integration/pull/491 to make sure bugs land in the right component? After removing the component config we set up a Jira automation based on the labels, which will now not be set.

[grahamalama]

Ahh I see. We can revert #491, or we can verify that Jira labels can be set on new issues, in which case we can flip sync_whiteboard_labels back to True. Do you have a preference either way?

[scholtzan]

Using components would be my preference

[grahamalama]

@scholtzan and I chatted about this on Slack but, it looks like this is working as expected.

https://bugzilla.mozilla.org/show_bug.cgi?id=1833668 triggered the creation of https://mozilla-hub.atlassian.net/jira/software/c/projects/DENG/issues/DENG-892, which included the component being set.

Closing this issue as resolved. @scholtzan, feel free to reopen if you see further issues.