[toggle-core] Update issue template for bugs using new issue form in a YAML file

[xserrat]

In order to make easier the creation of bugs following a specific format, we should update the markdown file into a YAML file.

See Github Docs.

This epic contains:

• [pheature-flags] Update issue template for bugs using new issue form in a YAML file #300
• [toggle-core] Update issue template for bugs using new issue form in a YAML file toggle-core#23
• [api-docs] Update issue template for bugs using new issue form in a YAML file api-docs#8
• [mezzio-toggle] Update issue template for bugs using new issue form in a YAML file mezzio-toggle#3
• [laravel-toggle] Update issue template for bugs using new issue form in a YAML file laravel-toggle#3
• [php-sdk] Update issue template for bugs using new issue form in a YAML file php-sdk#4
• [symfony-toggle] Update issue template for bugs using new issue form in a YAML file symfony-toggle#3
• [toggle-crud-psr11-factories] Update issue template for bugs using new issue form in a YAML file toggle-crud-psr11-factories#5
• [toggle-crud-psr7-api] Update issue template for bugs using new issue form in a YAML file toggle-crud-psr7-api#5
• [toggle-crud] Update issue template for bugs using new issue form in a YAML file toggle-crud#10
• [inmemory-toggle] Update issue template for bugs using new issue form in a YAML file inmemory-toggle#3
• [toggle-model] Update issue template for bugs using new issue form in a YAML file toggle-model#8
• [dbal-toggle] Update issue template for bugs using new issue form in a YAML file dbal-toggle#3
• [monorepo-changelog-filter] Update issue template for bugs using new issue form in a YAML file monorepo-changelog-filter#3
• [toggle-ui] Update issue template for bugs using new issue form in a YAML file toggle-ui#2

[pcs289]

How about using this bug_report YAML file found at toggle-ui PR#3 to have all ISSUE_TEMPLATES standardized? Otherwise, do you think we should customize bug_report templates on a per-repo basis?

[xserrat]

Ouch! I didn't see your comment. I've just merged the first issue regarding this epic and I named the file as bug.yml directly. What do you think? See https://github.com/pheature-flags/pheature-flags/blob/1.0.x/.github/ISSUE_TEMPLATE/bug.yml . We could use a similar structure.

Regarding the customisation, I agree with you that we could customise them. For the issue #300 that it was a bug report for the pheature-flags repo, I've added a section called Integration with a dropdown of the three possible integrations: Standalone, Symfony, Mezzio and Laravel. I think that for Toggle UI we could set a dropdown for each component maybe... @kpicaza what do you think about that?

[xserrat]

@pcs289 , check also the https://github.com/pheature-flags/pheature-flags/blob/1.0.x/.github/ISSUE_TEMPLATE/bug.yml. I've set the two suggested labels bug and triage. The triage is added in order to help maintainers to filter by those issues pending to check by maintainers. I think that it's a good way to keep control about incoming bugs. After checking the bug and ensure that it's a real bug, we can remove the triage label to mark as "real bug". What do you think?

[pcs289]

@xserrat I am using the template at PR#3 for toggle-ui as the Integration dropdown is not needed.

[pcs289]

🚀