You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by "mfrancisc (via GitHub)" <gi...@apache.org> on 2026/08/19 13:31:56 UTC
[PR] fix(jira): keep changelog items that share a field in one history entry (#9057) [devlake]
mfrancisc opened a new pull request, #9062:
URL: https://github.com/apache/devlake/pull/9062
## Summary
- Jira often emits multiple changelog items with the same `field` in one history entry (add/remove of `Fix Version`, `Component`, `labels`, etc.). `_tool_jira_issue_changelog_items` was keyed by `(connection_id, changelog_id, field)`, so the extractor silently kept only one row.
- Add a per-field `item_index` to the primary key. Indexes are assigned from item content (from/to values and strings), not JSON array order, so re-extract of the same changelog stays stable if Jira reshuffles `items`.
- Domain `issue_changelogs.id` includes `item_index`. The migration rebuilds the PK, resets Jira extract/convert subtask state so the next pipeline re-extracts from existing raw JSON, and drops old domain rows that used the previous id format.
Fixes #9057
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org