---
name: Bug report
about: A reproducible problem
title: ''
labels: bug
assignees: ''

---

Good bug reports include a failing test! Writing a test helps you to isolate and describe the problem, and it helps us to fix it fast. Bug reports without a failing test or reproduction steps are likely to be closed.

Here’s an example test to get you started.

          close-issue-reason: not_planned

          # PULL REQUESTS -----------------------------------------------------
          days-before-pr-stale: 30
          exempt-pr-labels: "from:contributor"
          stale-pr-label: stale
          stale-pr-message: >
            This pull request has been automatically marked as stale because it has not had recent activity.

      options:
        - label: I checked that this language is not already being translated in FastAPI docs.
          required: true
        - label: I searched existing discussions to ensure no one else proposed this language.
          required: true
        - label: I am a native speaker of the language I want to help translate.
          required: true
  - type: input
    id: language
    attributes:

---
name: Test Failure
about: A test failure in CI
labels: ">test-failure"

---

<!--
Please fill out the following information, and ensure you have attempted
to reproduce locally
-->

**Build scan**:

**Repro line**:

**Reproduces locally?**:

**Applicable branches**:

**Failure history**:
<!--
Link to build stats and possible indication of when this started failing and how often it fails

          github-hooks: true
          status-context: elasticsearch-ci/{pr-job}
          cancel-builds-on-update: true
          excluded-regions:
            - ^docs/.*
          black-list-labels:
            - '>test-mute'
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'
          properties-content: |
            JAVA_HOME=$HOME/.java/$ES_BUILD_JAVA

---
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''

---

(_Please see [discuss.codelibs.org](https://discuss.codelibs.org/c/FessEN/8) before filing a bug._)

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

          white-list-target-branches:
            - master
          excluded-regions:
            - ^docs/.*
          black-list-labels:
            - '>test-mute'
            - ':Delivery/Packaging'
    axes:
      - axis:
          type: label-expression
          name: os
          values:
            - "windows-2019"
      - axis:
          type: user-defined
          name: PACKAGING_TASK

  - type: textarea
    id: actual-behavior
    attributes:
      label: "What did you see happen?"
    validations:
      required: true
  - type: textarea
    id: expected-behavior
    attributes:
      label: "What did you expect to see?"
    validations:
      required: true
  - type: textarea
    id: editor-and-settings
    attributes:
      label: "Editor and settings"

    validations:
      required: true
  - type: textarea
    id: reproduce-latest-version
    attributes:
      label: "Does this issue reproduce at the latest version of golang.org/x/vuln?"
    validations:
      required: true
  - type: textarea
    id: go-env
    attributes:
      label: "Output of `go env` in your module/workspace:"
      render: shell
    validations:
      required: true
  - type: textarea

src/main/resources/
├── fess_config.properties     # Main configuration
├── app.xml, fess.xml          # DI configuration
├── fess_*.xml                 # Feature-specific DI
├── fess_label_*.properties    # UI labels (i18n)
├── fess_message_*.properties  # Validation messages (i18n)
└── fess_indices/              # OpenSearch index mappings

src/main/webapp/WEB-INF/view/  # JSP templates