Merge pull request #3 from ADORSYS-GIS/fpo-issue-template

Adding issue templates from keycloak

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,112 @@
+name: Bug Report
+description: Report a non-security sensitive bug in Keycloak
+labels: ["kind/bug", "status/triage"]
+body:
+  - type: checkboxes
+    attributes:
+      label: Before reporting an issue
+      description: |
+        Please search to see if the issue is already reported, and try to reproduce the issue on the latest release.
+
+        Any reported issues must be reproducible in the [latest](https://github.com/keycloak/keycloak/releases/latest) or [nightly](https://github.com/keycloak/keycloak/releases/nightly) version of Keycloak.
+
+        **⚠️ Failing to follow these guidelines may result in your issue being closed without action. ⚠️**
+      options:
+        - label: I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
+          required: true
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      description: Affected area
+      options:
+        - 
+        - account/api
+        - account/ui
+        - adapter/fuse
+        - adapter/java-cli
+        - adapter/javascript
+        - adapter/jee
+        - adapter/jee-saml
+        - adapter/spring
+        - admin/api
+        - admin/cli
+        - admin/fine-grained-permissions
+        - admin/ui
+        - admin/client-java
+        - admin/client-js
+        - authentication
+        - authentication/webauthn
+        - authorization-services
+        - ci
+        - core
+        - dependencies
+        - dist/quarkus
+        - docs
+        - identity-brokering
+        - import-export
+        - infinispan
+        - ldap
+        - login/ui
+        - oidc
+        - oid4vc
+        - operator
+        - organizations
+        - saml
+        - storage
+        - testsuite
+        - token-exchange
+        - translations
+        - user-profile
+        - welcome/ui
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug
+      description: Provide a clear and concise description of what the problem is.
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: What version of Keycloak are you running?
+    validations:
+      required: true
+  - type: checkboxes
+    id: regression
+    attributes:
+      label: Regression
+      description: Was the issue introduced only after upgrading Keycloak, and it worked as expected in the past?
+      options:
+        - label: The issue is a regression
+  - type: textarea
+    id: behaviorExpected
+    attributes:
+      label: Expected behavior
+      description: Describe the expected behavior clearly and concisely.
+    validations:
+      required: true
+  - type: textarea
+    id: behaviorActual
+    attributes:
+      label: Actual behavior
+      description: Describe the actual behavior clearly and concisely.
+    validations:
+      required: true
+  - type: textarea
+    id: reproducer
+    attributes:
+      label: How to Reproduce?
+      description: Provide clear and concise steps to reproduce the problem.
+    validations:
+      required: true
+  - type: textarea
+    id: other
+    attributes:
+      label: Anything else?
+      description: Links? References? Anything that will give us more context about the issue you are encountering!
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Discussions
+    url: https://github.com/keycloak/keycloak/discussions
+    about: Propose new ideas, provide feedback, or ask for help here
+  - name: User mailing list
+    url: https://groups.google.com/forum/#!forum/keycloak-user
+    about: Ask and answer questions here 
+  - name: Developer mailing list 
+    url: https://groups.google.com/forum/#!forum/keycloak-dev
+    about: Propose new features and join in design discussions here

.github/ISSUE_TEMPLATE/enhancement.yml

@@ -0,0 +1,35 @@
+name: Enhancement Request
+description: Request an enhancement to an existing feature
+labels: ["kind/enhancement", "status/triage"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the enhancement at a high-level.
+    validations:
+      required: true
+  - type: input
+    id: discussion
+    attributes:
+      label: Discussion
+      description: |
+        If there has been a discussion around the enhancement, provide a link to the discussion.
+
+        Please note that larger enhancements should be discussed through [GitHub Discussion](https://github.com/keycloak/keycloak/discussions/categories/ideas).
+    validations:
+      required: false
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Describe why the feature should be added.
+    validations:
+      required: false
+  - type: textarea
+    id: details
+    attributes:
+      label: Details
+      description: More details? Implementation ideas? Anything that will give us more context about the enhancement you are proposing!
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/epic.yml

@@ -0,0 +1,36 @@
+name: Epic
+description: A large feature that is broken down into multiple linked issues.
+labels: ["kind/epic", "status/triage"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the feature at a high-level.
+    validations:
+      required: true
+  - type: input
+    id: discussion
+    attributes:
+      label: Discussion
+      description: |
+        Provide a link to the GitHub Discussion for the feature.
+    validations:
+      required: true
+  - type: textarea
+    id: issues
+    attributes:
+      label: Issues
+      description: List the issues related to this epic.
+      placeholder: |
+        - #1
+        - #2
+    validations:
+      required: false
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Provide a brief explanation of why the feature should be added.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,35 @@
+name: Feature Request
+description: Request a new feature to be added to Keycloak
+labels: ["kind/feature", "status/triage"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the feature at a high-level.
+    validations:
+      required: true
+  - type: input
+    id: discussion
+    attributes:
+      label: Discussion
+      description: |
+        If there has been a discussion around the feature, provide a link to the discussion.
+
+        Please note that all, except small requests, should be discussed through [GitHub Discussion](https://github.com/keycloak/keycloak/discussions/categories/ideas).
+    validations:
+      required: false
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Describe why the feature should be added.
+    validations:
+      required: false
+  - type: textarea
+    id: details
+    attributes:
+      label: Details
+      description: Design ideas? Implementation ideas? Anything that will give us more context about the feature you are proposing!
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/task.yml

@@ -0,0 +1,11 @@
+name: Task
+description: Any tasks that are not directly adding a new feature, enhancement or fixing a bug
+labels: ["kind/task"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe the task.
+    validations:
+      required: true