Errors occur when linked Jira issue does not match project in config about jira-bugzilla-integration HOT 3 CLOSED

configuration is changed to associate [foo] with project BAR

Did this actually happen? This is what setup the eventual Sentry issue?

from jira-bugzilla-integration.

In #636, the approach is to ignore the case where the linked Jira issue on a bug doesn't match the project that the whiteboard tag is configured with. e.g

• bug 9999 has a Jira link pointing to a project FOO
• the whiteboard tag on the bug is configured to be associated with project BAR
• since there is a mismatch, we ignore the bug update

Should we instead (or maybe follow up after #636 is landed) "move" the Jira issue? Since there is a mismatch, we delete the issue from project FOO and recreate it in project BAR. Unfortunately, it doesn't look like there's an API endpoint to do this. It's currently under consideration by the JIRA team.

This might be something to ask customers about.

from jira-bugzilla-integration.

Did this actually happen? This is what setup the eventual Sentry issue?

Since customer said that FNXV2 was the legacy Jira project for FXDROID, I thought it did.

But it wasn't exactly this, it's just that a user added manually both the tag and the link to Jira on the bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1794872#a13307585_430528

We don't do anything to prevent any of the two possible scenarios, so it must be handled.

Should we instead (or maybe follow up after #636 is landed) "move" the Jira issue?

If there was an easy way, why not, but so far ignoring seems to be the safest.

Since there is a mismatch, we delete the issue from project FOO and recreate it in project BAR.

But we would potentially loose history, or extra stuff like comments, attachments, etc.

This might be something to ask customers about.

Customer said "we don’t really even need to worry about an error, here, if it’d be possible for us to turn them off)" [...] "simply allowing this kind of component sync failure to happen, if the Jira ticket finds itself in a project that doesn’t contain a matching component)"

from jira-bugzilla-integration.