diff --git a/.github/ISSUE_TEMPLATE/release_issues22.md b/.github/ISSUE_TEMPLATE/release_issues22.md
deleted file mode 100644
index fb90a54a60..0000000000
--- a/.github/ISSUE_TEMPLATE/release_issues22.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-name: Testing Release Review Template
-about: Template for requesting a production release for VA mobile app
-title: "{{ env.releaseDate }} Release Sign-Off: {{ env.versionNumber }}"
-labels: release
-assignees: IsraelleHub
-
----
-
-# Release for {{ env.releaseDate }}
-This ticket is to control for all the requirements for the upcoming release before the Pull Request is opened. This should hold any tasks or bug fixes unique to the release branch. It should also collect any text for What's New and any content changes for the app stores.
-
-This ticket should be complete by {{ env.vaDueDate }}
-## Release Checklist
-
-- [ ] What's new content (App Store) - *required*
-- [ ] What's new content (In app/Alert Box) - *optional*
-- [ ] Content updates
-
-## Sign-offs: 
-<!-- All groups should check the box when they approve --> 
-- [ ] QA **Due {{ env.qaDueDate }}**
-- [ ] Product **Due {{ env.prodDueDate }}**
-- [ ] Mobile Release Manager **Due after 10am EST {{ env.vaDueDate }}** 
-
-## Release version
-<!-- Automated value, do not change -->
-{{ env.versionNumber }}
-
-## What's New content (App Store) - *required*
-<!-- Define the content for the What's New sections of the app stores here -->
-If there aren't any new features, use standard messaging: We added general improvements and fixed a few bugs.
-
-If a Flagship team decides to update the App Stores What's New content, their work should be done in a ticket and provided to the release manager, who will then update this section. If not provided, it's assumed not to be used. 
-
-## What's New content (In App/Alert Box) - *optional*
-<!-- Define the content for the What's New alert box here -->
-This work is to be completed by Flagship teams before RC branch is cut and completed by engineering. Flagship team to provide release manager with the ticket this work was completed in for reference. 
-
-## App Store content changes?
-All changes should be made to the files in the repo and not directly to the stores. 
-Indicate NA if no changes.
-
-- [ ] Images: 
-- [ ] Content:
-- [ ] Other (Privacy Policy, Promotions etc.):
-
-## Severe bugs:
-<!-- Link any severe bug tickets here and indicate if they need review or if they are scheduled/blocked. Reminder Sev-1 bugs to be fixed immediately, Sev-2 in 1 to 2 sprints after identified, and Sev-3 bugs to be prioritized using the team's tech debt capacity -->
-{{ env.issues }}
-
-## Regression Testing
-[QA Testrail Regression Test Run Here](^^^Testrail-url^^^)
-
diff --git a/.github/workflows/test22.yml b/.github/workflows/test22.yml
deleted file mode 100644
index 2fcb426192..0000000000
--- a/.github/workflows/test22.yml
+++ /dev/null
@@ -1,58 +0,0 @@
-# test build
-name: '[test] testing'
-on:
-  push:
-    branches:
-      - chanel-10312-create-release-coordination-ticket-on-github-not-zenhub
-jobs:
-  release_ticket:
-    runs-on: ubuntu-latest
-    outputs:
-      ticketNumber: ${{steps.create_issue.outputs.number}}
-      versionNumber: ${{env.VERSION}}
-      releaseDate: ${{env.RELEASE_DATE}}
-      qaDueDate: ${{env.QA_DUE_DATE}}
-      prodDueDate: ${{env.PROD_DUE_DATE}}
-      vaDueDate: ${{env.VA_DUE_DATE}}
-    steps:
-      - run: echo "VERSION=${GITHUB_REF##*/}" >> $GITHUB_ENV
-      - run: echo "QA_DUE_DATE=$(date -d "+2 days" '+%A %b %d, %Y')" >> $GITHUB_ENV
-      - run: echo "PROD_DUE_DATE=$(date -d "+5 days" '+%A %b %d, %Y')" >> $GITHUB_ENV
-      - run: echo "VA_DUE_DATE=$(date -d "+6 days" '+%A %b %d, %Y')" >> $GITHUB_ENV
-      - run: echo "RELEASE_DATE=$(date -d "+13 days" '+%A %b %d, %Y')" >> $GITHUB_ENV
-      - uses: actions/checkout@v3
-      - run: echo "${{ secrets.GH_ACTIONS_PAT }}" > token.txt
-      - run: gh auth login --with-token < token.txt
-      - run: |
-          sev1=$(gh issue list -l "sev-1" --jq 'map("|#\(.number)|\(.title)|") | join("\n") ' --json number,title)
-          sev2=$(gh issue list -l "sev-2" --jq 'map("|#\(.number)|\(.title)|") | join("\n") ' --json number,title)
-          header='| Issue | Title | Notes |
-          |-------|-------|-------|
-          '
-          table="${header}${sev1}${sev2}"
-          echo 'TABLE<<EOF' >> $GITHUB_ENV
-          echo "${table}" >> $GITHUB_ENV
-          echo 'EOF' >> $GITHUB_ENV
-      - name: Create Release Ticket
-        uses: JasonEtco/create-an-issue@v2
-        with:
-          filename: .github/ISSUE_TEMPLATE/release_issues22.md
-        env:
-          versionNumber: ${{ env.VERSION }}
-          qaDueDate: ${{env.QA_DUE_DATE}}
-          prodDueDate: ${{env.PROD_DUE_DATE}}
-          vaDueDate: ${{env.VA_DUE_DATE}}
-          releaseDate: ${{ env.RELEASE_DATE }}
-          issues: ${{ env.TABLE }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        id: create_issue
-      - name: Assign Users to Release Ticket
-        if: ${{ success() }}
-        run: |
-          # Fetch GitHub Group Members
-          TEAM_MEMBERS=$(gh api orgs/department-of-veterans-affairs/teams/flagship-mobile-release-approvers/members --jq 'map(.login) | join(",")')
-          ASSIGNEES=$(echo $TEAM_MEMBERS | paste -sd "," -)
-          ISSUE_NUMBER=${{ steps.create_issue.outputs.number }}
-          gh issue edit $ISSUE_NUMBER --add-assignee $ASSIGNEES
-        env:
-          GITHUB_TOKEN: ${{ secrets.GH_ACTIONS_PAT }} 
\ No newline at end of file