Skip to content

Remove updated_at field from latest issues transform unique keys. #15727

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 9 commits into from
Oct 22, 2025
Merged

Remove updated_at field from latest issues transform unique keys. #15727

merged 9 commits into from
Oct 22, 2025

Conversation

@clement-fouque
Copy link
Contributor

@clement-fouque clement-fouque commented Oct 22, 2025 •
edited
Loading

Proposed commit message

In the latest version 2.17.1, I misunderstood the behaviour of the transform and introduced a new bug. The unique key should be on the issue ID only and not on the issue ID and update_at fields.

This PR is fixing the issue.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@clement-fouque clement-fouque changed the title GitHub issues improve transform Remove updated_at field from latest issues transform unique keys. Oct 22, 2025
@clement-fouque clement-fouque added the bug Something isn't working, use only for issues label Oct 22, 2025
@clement-fouque clement-fouque marked this pull request as ready for review October 22, 2025 21:11
@clement-fouque clement-fouque requested a review from a team as a code owner October 22, 2025 21:11
@clement-fouque clement-fouque enabled auto-merge (squash) October 22, 2025 21:12
@clement-fouque clement-fouque added bugfix Pull request that fixes a bug issue and removed bug Something isn't working, use only for issues labels Oct 22, 2025
@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Oct 22, 2025

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@clement-fouque clement-fouque merged commit 58fefb8 into main Oct 22, 2025
7 checks passed
@elasticmachine
Copy link

elasticmachine commented Oct 22, 2025

💚 Build Succeeded

@clement-fouque clement-fouque deleted the github_issues_improve_transform branch October 22, 2025 21:55
@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Oct 22, 2025

Package github - 2.17.2 containing this change is available at https://epr.elastic.co/package/github/2.17.2/

agithomas pushed a commit to agithomas/integrations that referenced this pull request Oct 30, 2025
@clement-fouque @agithomas
Remove updated_at field from latest issues transform unique keys. (el…
92d2e03 
…astic#15727)

* refactor(transform): update unique keys for latest issues and bump version to 2.0.0

* refactor(transform): bump version to 2.17.0 and update changelog with bugfix details

* chore(manifest): bump version to 2.18.0

* chore: update version to 2.17.1 and enhance changelog description for unique keys transformation

* Remove updated_at field from latest transform unique key

* changelog: add bugfix entry for removing updated_at field; update version to 2.17.2 in manifest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@efd6 efd6 efd6 approved these changes

Assignees

No one assigned

Labels

bugfix Pull request that fixes a bug issue Integration:github GitHub

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@clement-fouque @elasticmachine @efd6 @andrewkroh