Feat/adm 633

.buildkite/pipeline.yml

@@ -11,9 +11,15 @@ steps:
     command: ./ops/check.sh security
 
   - label: ":white_check_mark: Check Backend"
+    if: build.branch == "main" && build.message =~ /(?i)\[backend\]/
     key: "check-backend"
     command: ./ops/check.sh backend
 
+  - label: ":white_check_mark: Check Frontend"
+    if: build.branch == "main" && build.message =~ /(?i)\[frontend\]/
+    key: "check-frontend"
+    command: ./ops/check.sh frontend
+
   - label: ":mag: Check Frontend License"
     key: "check-frontend-license"
     commands: ./ops/check.sh frontend-license
@@ -29,11 +35,12 @@ steps:
           expire_in: "${RETENTION_DAYS} days"
 
   - label: ":cloudformation: Deploy infra"
-    if:  build.branch == "main" && build.message =~ /\[infra\]/
+    if: build.branch == "main" && build.message =~ /(?i)\[infra\]/
     key: "deploy-infra"
     depends_on:
       - "check-shell"
       - "check-security"
+      - "check-frontend"
       - "check-backend"
       - "check-frontend-license"
       - "check-backend-license"
@@ -44,31 +51,31 @@ steps:
     command: ./ops/deploy.sh infra
 
   - label: ":react: Build Frontend"
-    if:  build.branch == "main" && build.message =~ /\[frontend\]/
+    if: build.branch == "main" && build.message =~ /(?i)\[frontend\]/
     key: "build-frontend"
     depends_on: "deploy-infra"
     command: ./ops/build.sh frontend
 
   - label: ":java: Build Backend"
-    if:  build.branch == "main" && build.message =~ /\[backend\]/
+    if: build.branch == "main" && build.message =~ /(?i)\[backend\]/
     key: "build-backend"
     depends_on: "deploy-infra"
     command: ./ops/build.sh backend
 
   - label: ":rocket: Build Stub"
-    if:  build.branch == "main" && build.message =~ /\[stub\]/
+    if: build.branch == "main" && build.message =~ /(?i)\[stub\]/
     key: "build-stub"
     depends_on: "deploy-infra"
     command: ./ops/build.sh stub
 
   - label: ":rocket: Deploy Stub"
-    if:  build.branch == "main" && build.message =~ /\[stub\]/
+    if: build.branch == "main" && build.message =~ /(?i)\[stub\]/
     key: "deploy-stub"
     depends_on: "build-stub"
     command: ./ops/deploy.sh stub
 
   - label: ":rocket: Deploy e2e"
-    if: build.branch == "main" && (build.message =~ /\[frontend\]/ || build.message =~ /\[backend\]/)
+    if: build.branch == "main" && (build.message =~ /(?i)\[frontend\]/ || build.message =~ /(?i)\[backend\]/)
     key: "deploy-e2e"
     depends_on:
       - "build-frontend"
@@ -83,6 +90,7 @@ steps:
       - "deploy-stub"
       - "check-shell"
       - "check-security"
+      - "check-frontend"
       - "check-backend"
       - "check-frontend-license"
       - "check-backend-license"
@@ -95,6 +103,6 @@ steps:
           expire_in: "${RETENTION_DAYS} days"
 
   - label: ":rocket: Deploy prod"
-    if: build.branch == "main" && (build.message =~ /\[frontend\]/ || build.message =~ /\[backend\]/)
+    if: build.branch == "main" && (build.message =~ /(?i)\[frontend\]/ || build.message =~ /(?i)\[backend\]/)
     depends_on: "check-e2e"
     command: ./ops/deploy.sh prod

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -14,16 +14,65 @@ body:
 
       For non-technical support or general questions, you can email [heartbeat-dev@thoughtworks.com](mailto:heartbeat-dev@thoughtworks.com).
 
-      Also try to search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue using the form below instead of commenting on the old issue.
+      Also try to search your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue using the form below instead of commenting on the old issue.
+
+      Last please double confirm that you had already verified it can be replicated in the latest version, otherwise use the latest stable version could be the fastest way to resolve your issue.
 
 - type: input
+  id: contact
+  attributes:
+    label: Contact Details
+    description: How can we get in touch with you if we need more info?
+    placeholder: ex. email@example.com or full name that we can connect you in Slack or WeCom
+  validations:
+    required: true
+
+- type: input
+  id: version
   attributes:
     label: Version
     description: |
-      Check if the issue is reproducible with the latest stable version of Heartbeat.
-    placeholder: |
-      e.g. latest
+      What version of our software are you running? There is two methods to get the current version:
+        1. you can see the version info at the left top of the heartbeat pages
+        2. If you could not get the version, you can input "1.0.0" as well
+  validations:
+    required: true
+
+- type: dropdown
+  id: browsers
+  attributes:
+    label: What browsers are you seeing the problem on?
+    multiple: true
+    options:
+      - Firefox
+      - Chrome
+      - Safari
+      - Microsoft Edge
+
+- type: dropdown
+  id: page
+  attributes:
+    label: Pages
+    description: Which page you met this issue in?
+    multiple: true
+    options:
+      - Config
+      - Metrics
+      - Report
+    default: 0
+  validations:
+    required: true
 
+- type: dropdown
+  id: tool
+  attributes:
+    label: Tools
+    description: What tools your issue is related to?
+    multiple: true
+    options:
+      - Board
+      - Pipeline Tool
+      - Source Control
   validations:
     required: true
 
@@ -32,11 +81,9 @@ body:
     label: Summary
     description: |
       Please give us some info about your bug.
-
     placeholder: |
       1. I want to get the metrics report, but failed.
       2. ......
-
   validations:
     required: true
 
@@ -45,19 +92,17 @@ body:
     label: Steps to Reproduce
     description: |
       What do we need to do after opening your repo in order to make the bug happen? Clear and concise reproduction instructions are important for us to be able to triage your issue in a timely manner. Note that you can use [Markdown](https://guides.github.com/features/mastering-markdown/) to format lists and code.
-
     placeholder: |
       1. What's you input? Mask sensitive data
       2. What's you select?
       3. ......
-
   validations:
     required: true
 
 - type: textarea
   attributes:
     label: Current Behavior
-    description: A concise description of what you're experiencing.
+    description: A concise description of what you're experiencing and upload the screenshots.
   validations:
     required: true
 
@@ -68,26 +113,10 @@ body:
   validations:
     required: true
 
-- type: textarea
-  attributes:
-    label: Environment
-    description: |
-      e.g.
-        - **OS**: macOS Monterey
-        - **Browser**: Chrome 96.0.4664.55
-    value: |
-        - OS:
-        - Browser:
-    render: markdown
-
-  validations:
-    required: false
-
 - type: textarea
   attributes:
     label: Any additional comments?
     description: |
       e.g. some background/context of how you ran into this bug.
-
   validations:
     required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -16,14 +16,22 @@ body:
 
               Also try to search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue using the form below instead of commenting on the old issue.
 
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com or full name that we can connect you in Slack or WeCom
+    validations:
+      required: true
+
   - type: textarea
     attributes:
       label: Summary - What problem does this feature solve?
       description: |
         Explain your use case, context, and rationale behind this feature request. More importantly, what is the end user experience you are trying to build that led to the need for this feature?
 
         An important design goal of Heartbeat is keeping the API surface small and straightforward. In general, we only consider adding new features that solve a problem that cannot be easily dealt with using existing APIs (i.e. not just an alternative way of doing things that can already be done). The problem should also be common enough to justify the addition.
-
     validations:
       required: true
 
@@ -38,3 +46,16 @@ body:
         3. ......
     validations:
       required: true
+
+  - type: dropdown
+    id: tool
+    attributes:
+      label: Tools
+      description: What tools will support your request feature?
+      multiple: true
+      options:
+        - Board
+        - Pipeline Tool
+        - Source Control
+    validations:
+      required: true