Skip to content
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.

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

[Bug]: Default issue tracker template for Gitlab to not be the default template used #12

Closed
Syakyr opened this issue Jan 24, 2024 · 1 comment · Fixed by #16
Closed
Assignees
Labels
documentation Improvements or additions to documentation ready Ready to be merged and closed
Milestone

Comments

@Syakyr
Copy link
Collaborator

Syakyr commented Jan 24, 2024

Problem Domain

Gitlab

OS/Platform(s) Used

None

Problem Brief

Having the current issue template to be the default in Gitlab breaks some conventions with regards to how the issue tracker is being used across different teams. So it has to be that the issue template should be an option instead of being the default.

Steps to Reproduce

  • Create a new issue in Gitlab after creation of a repository using this template

Expected Result

Empty template

Actual Result

Filled template with it being the default

@Syakyr Syakyr added bug Something isn't working triage To be looked at by one of the maintainers to see where this issue lies labels Jan 24, 2024
@Syakyr
Copy link
Collaborator Author

Syakyr commented Jan 24, 2024

@Syakyr Syakyr added documentation Improvements or additions to documentation and removed bug Something isn't working triage To be looked at by one of the maintainers to see where this issue lies labels Jan 25, 2024
@Syakyr Syakyr linked a pull request Jan 26, 2024 that will close this issue
@Syakyr Syakyr added the ready Ready to be merged and closed label Jan 26, 2024
@Syakyr Syakyr added this to the 0.2.2 release milestone Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation ready Ready to be merged and closed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants