Skip to content

Conversation

mohitjha-elastic
Copy link
Collaborator

Proposed Commit Message

atlassian_jira and atlassian_confluence: fix time parsing in cursor logic.

After reviewing the live request tracer, it was observed that the timestamps from Atlassian Jira Cloud include a
timezone offset (+0000), which was not being parsed correctly. To fix this, the expected timestamp layout
was added in parseDate.

Additionally, the expected timestamp layouts were added in formatDate for both Atlassian Jira and Atlassian Confluence
to ensure the full timestamp is captured accurately.

Tested the changes using mock server and the data available in the test folder.

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.

How to test this PR locally

To test atlassian_jira integration

Clone integrations repo.
Install the elastic package locally.
Start the elastic stack using the elastic package.
Move to integrations/packages/atlassian_jira directory.
Run the following command to run tests.
elastic-package test -v

To test atlassian_confluence integration

Clone integrations repo.
Install the elastic package locally.
Start the elastic stack using the elastic package.
Move to integrations/packages/atlassian_confluence directory.
Run the following command to run tests.
elastic-package test -v

Related issues

  • It relates to sdh beats Issue 5901

@mohitjha-elastic mohitjha-elastic added Integration:atlassian_jira Atlassian Jira (Community supported) Integration:atlassian_confluence Atlassian Confluence (Community supported) bugfix Pull request that fixes a bug issue Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] Team:Sit-Crest Crest developers on the Security Integrations team [elastic/sit-crest-contractors] labels May 5, 2025
@mohitjha-elastic mohitjha-elastic self-assigned this May 5, 2025
@mohitjha-elastic mohitjha-elastic requested a review from a team as a code owner May 5, 2025 12:27
@elasticmachine
Copy link

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

cc @mohitjha-elastic

Copy link

@kcreddy kcreddy merged commit e3468cd into elastic:main May 5, 2025
7 checks passed
@elastic-vault-github-plugin-prod

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

@elastic-vault-github-plugin-prod

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

@mohitjha-elastic mohitjha-elastic deleted the fix-time-parsing-lassian_jira-and-atlassian_confluence branch May 15, 2025 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Pull request that fixes a bug issue Integration:atlassian_confluence Atlassian Confluence (Community supported) Integration:atlassian_jira Atlassian Jira (Community supported) Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] Team:Sit-Crest Crest developers on the Security Integrations team [elastic/sit-crest-contractors]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants