Skip to content

chore: add Environment field to bug report template #9864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
datamweb wants to merge 3 commits into
base: develop
Choose a base branch
from
+14 −0
Open

chore: add Environment field to bug report template #9864

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a8f6c92
chore: add Environment field to bug report template
datamweb Jan 2, 2026
c07fa24
chore: enable multi-select for environment in bug report form
datamweb Jan 2, 2026
665ceff
chore: add self-env
datamweb Jan 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,20 @@ body:
validations:
required: true

- type: dropdown
id: environment
attributes:
label: Environment
description: Which CI_ENVIRONMENT setting are you using?
multiple: true
options:
Copy link
Member

@paulbalandan paulbalandan Jan 2, 2026

Choose a reason for hiding this comment

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

This should be multi-select options as the bug can occur in multiple envs.

Copy link
Contributor Author

@datamweb datamweb Jan 2, 2026

Choose a reason for hiding this comment

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

Done!

Copy link
Collaborator

@ddevsr ddevsr Jan 2, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

when self-env? i think must have it

Copy link
Member

@paulbalandan paulbalandan Jan 2, 2026

Choose a reason for hiding this comment

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

"self-env" in itself seems vague. is there a way to write it like "others, please specify" with a text box for that others?

Copy link
Contributor Author

@datamweb datamweb Jan 2, 2026

Choose a reason for hiding this comment

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

It seems that GitHub currently do not support conditional logic (showing a field dependent on a specific choice).

https://github.com/orgs/community/discussions/4386

To implement this, we would have to add a separate input field that is always visible (though optional).

I'm not personally fond of this approach as it clutters the form for users who don't need it. Given this limitation, would you still like me to add it?

Copy link
Contributor

@neznaika0 neznaika0 Jan 2, 2026

Choose a reason for hiding this comment

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

"personal" is quite a normal option. We may not know the full settings for this environment anyway. Therefore, knowing that the environment is configured differently, you can ask questions to the OP. No need to complicate things.

When I open the issue, I'm a little confused by the many descriptions. Especially, when the error is small.

Copy link
Member

@michalsn michalsn Jan 3, 2026

Choose a reason for hiding this comment

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

Instead of self-env, can we make it Other (custom)?

- production
- development
- testing
- self-env
validations:
required: true

- type: input
id: database
attributes:
Expand Down