# New issue reporting templates

**URL:** https://discourse.itk.org/t/new-issue-reporting-templates/1720
**Category:** Community
**Tags:** github
**Created:** [March 29, 2019, 8:04pm UTC](https://discourse.itk.org/t/new-issue-reporting-templates/1720 "2019-03-29T20:04:58Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![matt.mccormick](https://discourse.itk.org/user_avatar/discourse.itk.org/matt.mccormick/32/7_2.png) [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [March 29, 2019, 8:04pm UTC](https://discourse.itk.org/t/new-issue-reporting-templates/1720/1 "2019-03-29T20:04:58Z")

</div>

Special recognition and thanks go to @jhlegarreta, who did an awesome job improving our GitHub issue reporting templates. 🎩 👏

Now, when [creating a new issue](https://github.com/InsightSoftwareConsortium/ITK/issues/new/choose), a menu of categories is presented:

 ![image](https://discourse.itk.org/uploads/default/original/1X/c12e7820362b703d96e379435f58c9198135d137.png)

and the issue is pre-populated with guidance material and a template of suggested content.

Thank you @jhlegarreta!

---

<div class="post-metadata">

### Author: ![jhlegarreta](https://discourse.itk.org/user_avatar/discourse.itk.org/jhlegarreta/32/476_2.png) [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)
#### Post date: [March 29, 2019, 8:25pm UTC](https://discourse.itk.org/t/new-issue-reporting-templates/1720/2 "2019-03-29T20:25:55Z")

</div>

You’re welcome.

Making ITK smarter and the tools it uses even more welcoming is always fulfilling.

---

<div class="post-metadata">

### Author: ![imikejackson](https://discourse.itk.org/user_avatar/discourse.itk.org/imikejackson/32/35_2.png) [@imikejackson](https://discourse.itk.org/u/imikejackson)
#### Post date: [March 30, 2019, 1:00pm UTC](https://discourse.itk.org/t/new-issue-reporting-templates/1720/3 "2019-03-30T13:00:53Z")

</div>

I the spirit of openness would you be able to post a short “how to” for other projects to use these templates for their own projects? This is awesome!!

---

<div class="post-metadata">

### Author: ![jhlegarreta](https://discourse.itk.org/user_avatar/discourse.itk.org/jhlegarreta/32/476_2.png) [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)
#### Post date: [March 30, 2019, 2:25pm UTC](https://discourse.itk.org/t/new-issue-reporting-templates/1720/4 "2019-03-30T14:25:41Z")

</div>

@imikejackson Thanks for appreciating it.

Will do. But allow me some time.

---

<div class="post-metadata">

### Author: ![jhlegarreta](https://discourse.itk.org/user_avatar/discourse.itk.org/jhlegarreta/32/476_2.png) [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)
#### Post date: [May 3, 2019, 8:29pm UTC](https://discourse.itk.org/t/new-issue-reporting-templates/1720/5 "2019-05-03T20:29:55Z")

</div>

@imikejackson There it is:

> [@Building strong ties in the community with GitHub Community Health Files](https://discourse.itk.org/t/building-strong-ties-in-the-community-with-github-community-health-files/1834):
>
> GitHub labels GitHub issues and pull requests can be labeled so that community members can clearly identify the areas the issues and contributions are related to. This helps a contributor grasp a clear picture of the tasks ahead, as well as a mechanism for organization. [Labels in ITK](https://github.com/InsightSoftwareConsortium/ITK/labels) are grouped into three categories: area: area of the toolkit affected by the issue or pull request. status: status of the issue or pull request for cases when further data is required to reproduce the…

---

<div class="post-metadata">

### Author: ![imikejackson](https://discourse.itk.org/user_avatar/discourse.itk.org/imikejackson/32/35_2.png) [@imikejackson](https://discourse.itk.org/u/imikejackson)
#### Post date: [May 6, 2019, 11:22am UTC](https://discourse.itk.org/t/new-issue-reporting-templates/1720/6 "2019-05-06T11:22:52Z")

</div>

Awesome post. This will be very helpful for other projects that would like to get something like this going.
