---
# System prepended metadata

title: Velero Community Issue / PR template
tags: [communication]

---

# closing an issue

## unable to recreate

Thank you for reporting this issue and providing the detailed information.  Unfortunately, we haven't been able to reproduce this bug on our end.  If you have any further information that might help us investigate further, please don't hesitate to add it here. For now, we'll be closing this issue.  Should you encounter this problem again, please feel free to reopen it or submit a new issue with updated details.

## not a priority to fix
Thank you for reporting this issue and for the detailed information you've provided.  We've discussed this issue internally, and while we understand it may be impacting your workflow, we've determined it's not a high priority for us to address at this time. This could be due to a number of factors, such as limited resources or the need to focus on other critical issues.

We appreciate your understanding. We will close the issue for now. If you are interested in further making a case for the bug to fixed please attend a [community call](https://hackmd.io/bxrvgewUQ5ORH10BKUFpxw) or ping us in [slack](https://kubernetes.slack.com/messages/velero) to allow for further discussion. If you are interested in contributing a fix, or if this issue becomes more critical for you, please let us know.

# closing a PR

## not a priority
Thanks for taking the time to submit this pull request and contribute to Velero! We appreciate you taking the initiative to improve the project.

After careful review, we've decided not to merge this pull request at this time. The proposed changes don't align with our current [roadmap/priorities](https://hackmd.io/iQy7XmPOT0y8lrCuAFL4PQ) for Velero.

We encourage you to continue contributing to Velero!  We're always looking for contributions, and there are many other areas where your skills and expertise could be valuable. Please don't hesitate to open new pull requests or join the discussions on other issues.  We value your involvement in the Velero community.

## old pr or pr needs too much work to continue
Thanks for taking the time to submit this pull request and contribute to Velero! We appreciate you taking the initiative to improve the project

We have some concerns about the approach taken in this PR, and we think it might introduce. Please ping us in [slack](https://kubernetes.slack.com/messages/velero) to discuss the issue further if needed.

We encourage you to continue contributing to Velero!  We're always looking for contributions, and there are many other areas where your skills and expertise could be valuable. Please don't hesitate to open new pull requests or join the discussions on other issues.  We value your involvement in the Velero community.


# New contributors to Velero

[new contributor list](http://api-monocle.wdh415-vpc-cluster-3626522b15eedb880d7b99992e225c1b-0000.us-south.containers.appdomain.cloud/upstream-velero/new_authors?q=from:now-6weeks)  * note http:// not https://

```
sangitaray2021	2
rvandernoort	1
mjnagel	1
mcluseau	1
jeremie-lesage	1
emmanuel-ferdman	1
df-cgdm	1
clcondorcet	1
chrisRedwine	1
```