# Jira native connector

**URL:** <https://discuss.elastic.co/t/jira-native-connector/373275>\
**Category:** Elastic Search\
**Tags:** connectors\
**Created:** [January 16, 2025, 11:59am UTC](https://discuss.elastic.co/t/jira-native-connector/373275 "2025-01-16T11:59:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Noam\_Huri](https://avatars.discourse-cdn.com/v4/letter/n/67e7ee/32.png) [@Noam\_Huri](https://discuss.elastic.co/u/Noam_Huri)\
**Post date:** [January 16, 2025, 11:59am UTC](https://discuss.elastic.co/t/jira-native-connector/373275/1 "2025-01-16T11:59:12Z")

</div>

I'm using a native connector to index my Jira, and I only get attachment items without bugs. I checked the user credentials, and the user could view bugs.

Any idea?

Thank you,  
Noam

---

<div class="post-metadata">

**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\
**Post date:** [January 16, 2025, 4:48pm UTC](https://discuss.elastic.co/t/jira-native-connector/373275/2 "2025-01-16T16:48:12Z")

</div>

Hi @Noam_Huri ,

Sorry you're having this issue. As an Elastic Cloud customer, you're entitled to support, so don't hesitate to reach out to them at [https://support.elastic.co](https://support.elastic.co). They can help by looking at your connectors logs, and investigating your connector settings/configuration.

In the mean time, can you provide some more information?

- do the syncs complete successfully, or are they failing? If they're failing, what's the error message?
- have you configured the right project keys where you're expecting to find Bugs?
- Do you have any Basic Sync Rules configured?
- Do you have any Advanced Sync Rules configured?
- Have you made any changes/customizations to your ingest pipeline?

Bug issues are definitely expected to be synced, so I'm trying to enumerate known ways they might be getting excluded or dropped before they get to Elasticsearch.

---

<div class="post-metadata">

**Author:** ![Noam\_Huri](https://avatars.discourse-cdn.com/v4/letter/n/67e7ee/32.png) [@Noam\_Huri](https://discuss.elastic.co/u/Noam_Huri)\
**Post date:** [January 19, 2025, 1:36pm UTC](https://discuss.elastic.co/t/jira-native-connector/373275/3 "2025-01-19T13:36:20Z")

</div>

The index did not work well becouse it has been exceeded the total fields [1000].

Thank you,  
Noam

---

<div class="post-metadata">

**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\
**Post date:** [January 21, 2025, 11:24pm UTC](https://discuss.elastic.co/t/jira-native-connector/373275/4 "2025-01-21T23:24:25Z")

</div>

Gotcha! Yep, that can happen. You have a few options here:

1. increase the max fields. I wouldn't recommend this, as it's fighting a losing battle. You probably hit 1000 fields because something in there is using dynamic strings as keys, so you'll eventually hit whatever limit you set.
2. Use Basic Sync Rules or Ingest Pipelines to drop fields that you don't care about, and/or rename fields to keep the field count low.
3. Change your mappings for the index to store the dynamic subset of your inputs as JSON blobs, rather than as objects with nesting fields.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 18, 2025, 11:24pm UTC](https://discuss.elastic.co/t/jira-native-connector/373275/5 "2025-02-18T23:24:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.