> For the complete documentation index, see [llms.txt](https://docs.gitconnector.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gitconnector.com/master/troubleshooting.md).

# Troubleshooting

{% stepper %}
{% step %}

### If your Git server is behind a firewall, make sure to whitelist the IP addresses used by GitConnector

{% content-ref url="/pages/ZTxoHYfx1kF6C1CSuQs8" %}
[IP whitelisting](/ip-whitelisting.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

### Organization repositories are not visible

1\. Go to your **GitHub** **Settings** page.

![](/files/yzLJ3uGyVLWJDVUewBfw)

2. Navigate to **Applications** and click on **GitConnector**.
3. Find your organization on the list and click **Grant**. If you do not see these buttons, then please switch to your organization account, navigate to **Third-party access**, and click on **Remove Restrictions**.
   {% endstep %}

{% step %}

### How to Hide the Default Development Panel in Jira Work Items

*Disabling unused development features helps reduce noise.*

[How To Remove or Edit Access to Development Panel from Jira Work Items](https://support.atlassian.com/jira/kb/how-to-remove-or-edit-access-to-development-panel-from-jira-issues/)

### 1. Remove the Development Field from Layout

This removes the panel from the issue UI.

**Steps:**

1. Go to **Project Settings → Work Items → Layout**
2. Find the **“Development”** field
3. Remove it from the layout

<figure><img src="/files/i3m7Ma5lQctCLwWutBRW" alt=""><figcaption></figcaption></figure>

### 2. Remove “View Development Tools” Permission

This ensures users cannot see development data even if the field exists.

**Steps:**

1. Go to **Jira Settings → Work Items → Permission Schemes**
2. Open your permission scheme&#x20;
3. Locate **“View Development Tools”**
4. Click **Remove**
5. Remove all groups, roles, or users

<figure><img src="/files/ejhjuTgaWuezkI6EZcTA" alt=""><figcaption></figcaption></figure>

### 3. Disconnect Unused Git Integrations

Even with permissions removed, integrations may still attach some data.
{% endstep %}
{% endstepper %}