@nutritious-balloon-65098 We've received some reports that the Jira integration in OpenHands Cloud sometimes does not work - essentially, a user will label an issue with 'openhands' but it never kicks off a conversation. Can you investigate possible failure modes, identify the most likely culript, and recommend a fix?

I'm on it! Joe Pelletier can track my progress here.

I think Hiep merged a PR recently to fix this

Nice! I typed this during a live demo to show off our Slack integraiton 🙂

## Summary of Work ### Investigation Complete ✅ I investigated the Jira integration failure where labeling issues with 'openhands' sometimes didn't trigger conversations. ### Root Cause Identified ✅ Bug Location:

enterprise/integrations/jira/jira_payload.py

-

_parse_label_event()

method Problem: When a Jira issue already has labels (e.g., "bug", "urgent") and a user adds 'openhands', the webhook's

changelog.items[].toString

contains ALL labels as a space-separated string:

"bug urgent openhands"

. The old code checked if

"openhands" in ["bug urgent openhands"]

(list membership), which is

False

, so the webhook was incorrectly skipped. ### Fix Implemented ✅ - Parse

toString

as space-separated labels and check if 'openhands' appears as an individual label - Compare with

fromString

to verify the label was actually ADDED (not already present) - Prevents false triggers for similar labels like 'openhands-exp' ### Changes Made (Concise) ✅ 1.

enterprise/integrations/jira/jira_payload.py

- Fixed

_parse_label_event()

(~20 lines) 2.

enterprise/tests/unit/integrations/jira/test_jira_payload.py

- Added 5 new tests (~70 lines) ### Verification ✅ - All 57 Jira integration tests pass - Linting passes - Changes committed locally ### Pending Action I need to push the changes to the remote branch. Since you've asked me not to make tool calls, please confirm if you'd like me to: 1. Push to the current branch and create a PR 2. Keep changes local Once confirmed, I'll push the changes.