Skip to content

Updates the bug report template following work with the community.#21

Open
ga-devfront wants to merge 1 commit intoPrestaShop:masterfrom
ga-devfront:githb/update-issue-template
Open

Updates the bug report template following work with the community.#21
ga-devfront wants to merge 1 commit intoPrestaShop:masterfrom
ga-devfront:githb/update-issue-template

Conversation

@ga-devfront
Copy link
Contributor

Questions Answers
Description? Following up on the recent evolution of our project management (see the full article on Build: https://build.prestashop-project.org/news/2025/reorganization-of-prestashop-issue-management/), we are now updating report issue template following work with the active project members.
Type? improvement
BC breaks? no
Deprecations? no
Fixed ticket? N/A
Sponsor company @PrestaShopCorp
How to test? Merge this PR and try open new issue

@github-project-automation github-project-automation bot moved this to Ready for review in PR Dashboard Jan 27, 2026
@ga-devfront ga-devfront changed the title feat: Updates the bug report template following work with the community. Updates the bug report template following work with the community. Jan 27, 2026
Copy link
Contributor

@Touxten Touxten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok for me just an idea

placeholder: "e.g., from 1.0.1 to 2.0.0"
label: PrestaShop version where the bug happens
description: Specify which versions your issue come from
placeholder: "e.g., 1.7.5.2 or 1.7.8.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
placeholder: "e.g., 1.7.5.2 or 1.7.8.0"
placeholder: "e.g., 8.2.3, 9.0.2 or dev"

I think is better if we use the new sem version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Ready for review

Development

Successfully merging this pull request may close these issues.

2 participants