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

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

diff --git a/README.md b/README.md
index b5ff1fb..0f25d9e 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,6 @@
   - [Requirements](#requirements)
   - [Usage](#usage)
   - [Update the Gemfile Lock](#update-the-gemfile-lock)
-  - [Submitting Issues](#submitting-issues)
   - [Releasing](#releasing)
   - [License](#license)
 
@@ -36,10 +35,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>.