From 9e31ed815f728fb17d4a7e4892c95b1485446c4d Mon Sep 17 00:00:00 2001
From: Jake Spain <jake.spain+15749776@perforce.com>
Date: Thu, 20 Apr 2023 08:51:12 -0400
Subject: [PATCH] Revert "Migrate issue management to Jira"

This reverts commit 2f0e817b7cd1e0c8a591218afa54252689eee230.
---
 README.md | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/README.md b/README.md
index 0529e18..b269094 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,6 @@
   - [Usage](#usage)
     - [Custom VM Config Attribute](#custom-vm-config-attribute)
   - [Update the Gemfile Lock](#update-the-gemfile-lock)
-  - [Submitting Issues](#submitting-issues)
   - [Releasing](#releasing)
   - [License](#license)
 
@@ -31,10 +30,6 @@ To update the `Gemfile.lock` run `./update-gemfile-lock`.
 
 Verify, and update if needed, that the docker tag in the script and GitHub action workflows matches what is used in the [vmpooler-deployment Dockerfile](https://github.com/puppetlabs/vmpooler-deployment/blob/main/docker/Dockerfile).
 
-## Submitting Issues
-
-Please file any issues or requests in Jira at <https://puppet.atlassian.net/jira/software/c/projects/POOLER/issues> where project development is tracked across all VMPooler related components.
-
 ## Releasing
 
 Follow these steps to publish a new GitHub release, and build and push the gem to <https://rubygems.org>.