This is an automated email from the ASF dual-hosted git repository.

github-actions[bot] pushed a commit to branch release/v1.1.0-incubating
in repository https://gitbox.apache.org/repos/asf/texera.git


The following commit(s) were added to refs/heads/release/v1.1.0-incubating by 
this push:
     new 26b378aa1e chore: trim issue templates (#4656)
26b378aa1e is described below

commit 26b378aa1e63dd0321cfd342512d763e84972c8c
Author: Yicong Huang <[email protected]>
AuthorDate: Sat May 2 07:06:04 2026 +0000

    chore: trim issue templates (#4656)
    
    ### What changes were proposed in this PR?
    
    - Drop the **Priority** dropdown from `feature-template.yaml` and
    `task-template.yaml`. Priority is tracked on the issue itself via
    GitHub's native field, so the in-template dropdown is redundant.
    `bug-template.yaml` never had one.
    - `bug-template.yaml`: replace the **Version** dropdown
    (`1.1.0-incubating (Pre-release/Master)` / `1.0.0`) with a **Branch**
    dropdown (`main` / `1.1.0-incubating`). Bugs are reported against
    branches more often than tagged releases.
    - `task-template.yaml`: tighten **Task Type**. Drop "Code
    Implementation" (every task is code) and add Performance + Other. Final
    list: Refactor / Cleanup, DevOps / Deployment / CI, Testing / QA,
    Documentation, Performance, Other.
    
    No other field changes.
    
    ### Any related issues, documentation, discussions?
    
    Closes #4655
    
    ### How was this PR tested?
    
    YAML parses locally for all three templates. Real-world test: open the
    "New issue" UI and confirm the dropdowns/labels render as expected once
    merged.
    
    ### Was this PR authored or co-authored using generative AI tooling?
    
    Generated-by: Claude Code (Opus 4.7)
    
    Co-authored-by: github-actions[bot] 
<github-actions[bot]@users.noreply.github.com>
    Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
    
    (backported from commit 592e6a3030fbbe12d37cbbe61fdebeac4f34346e)
---
 .github/ISSUE_TEMPLATE/bug-template.yaml     | 10 +++++-----
 .github/ISSUE_TEMPLATE/feature-template.yaml | 14 --------------
 .github/ISSUE_TEMPLATE/task-template.yaml    | 19 ++++---------------
 3 files changed, 9 insertions(+), 34 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug-template.yaml 
b/.github/ISSUE_TEMPLATE/bug-template.yaml
index 7a3ebc9202..ef0aefaa6e 100644
--- a/.github/ISSUE_TEMPLATE/bug-template.yaml
+++ b/.github/ISSUE_TEMPLATE/bug-template.yaml
@@ -40,13 +40,13 @@ body:
     validations:
       required: true
   - type: dropdown
-    id: version
+    id: branch
     attributes:
-      label: Version
-      description: What version of Texera are you running?
+      label: Branch
+      description: Which branch did you hit this on?
       options:
-        - 1.1.0-incubating (Pre-release/Master)
-        - 1.0.0
+        - main
+        - 1.1.0-incubating
       default: 0
     validations:
       required: true
diff --git a/.github/ISSUE_TEMPLATE/feature-template.yaml 
b/.github/ISSUE_TEMPLATE/feature-template.yaml
index f88d85b0f6..9551b9fa89 100644
--- a/.github/ISSUE_TEMPLATE/feature-template.yaml
+++ b/.github/ISSUE_TEMPLATE/feature-template.yaml
@@ -42,20 +42,6 @@ body:
     validations:
       required: true
 
-  - type: dropdown
-    id: impact
-    attributes:
-      label: Impact / Priority
-      description: How important is this feature?
-      options:
-        - (P0)Critical – blocks existing use cases
-        - (P1)High – significantly improves user experience
-        - (P2)Medium – useful enhancement
-        - (P3)Low – nice to have
-      default: 2
-    validations:
-      required: true
-
   - type: dropdown
     id: affected-area
     attributes:
diff --git a/.github/ISSUE_TEMPLATE/task-template.yaml 
b/.github/ISSUE_TEMPLATE/task-template.yaml
index 1e299fef7c..ef3977c03c 100644
--- a/.github/ISSUE_TEMPLATE/task-template.yaml
+++ b/.github/ISSUE_TEMPLATE/task-template.yaml
@@ -33,29 +33,18 @@ body:
     validations:
       required: true
 
-  - type: dropdown
-    id: priority
-    attributes:
-      label: Priority
-      description: How urgent or important is this task?
-      options:
-        - P0 – Critical
-        - P1 – High
-        - P2 – Medium
-        - P3 – Low
-      default: 2
-
   - type: checkboxes
     id: checklist
     attributes:
       label: Task Type
       description: Select the type of work involved.
       options:
-        - label: Code Implementation
-        - label: Documentation
         - label: Refactor / Cleanup
+        - label: DevOps / Deployment / CI
         - label: Testing / QA
-        - label: DevOps / Deployment
+        - label: Documentation
+        - label: Performance
+        - label: Other
 
   - type: markdown
     attributes:

Reply via email to