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

Customize Issue Templates #8

Closed
Tracked by #9
oliver-pham opened this issue Jan 8, 2022 · 4 comments · Fixed by #16
Closed
Tracked by #9

Customize Issue Templates #8

oliver-pham opened this issue Jan 8, 2022 · 4 comments · Fixed by #16
Assignees
Labels
difficulty:easy Issue that takes 1 - 3 days documentation Improvements or additions to documentation priority:medium Issue to be done in the current sprint
Projects

Comments

@oliver-pham
Copy link
Collaborator

oliver-pham commented Jan 8, 2022

Our templates may not be refined to our needs. Let's research, find, and suggest a better template here.

Current Feature request template:

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

Current Bug report template:

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser [e.g. stock browser, safari]
 - Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

Both

  1. Let's add a due date to each issue. This information is important, but GitHub doesn't provide any field/label for it.

Feature request

  1. I think we should add acceptance criteria. This should help reviewers design (manual) tests against PRs.

Bug report

  1. Add actual behavior (minhhang107)
@oliver-pham oliver-pham added the question Further information is requested label Jan 8, 2022
@oliver-pham oliver-pham added this to Backlog in Seeksi via automation Jan 8, 2022
@tuanthanh2067 tuanthanh2067 moved this from Backlog to To Do in Seeksi Jan 8, 2022
@oliver-pham oliver-pham mentioned this issue Jan 8, 2022
4 tasks
@tuanthanh2067
Copy link
Owner

For issue, I think we should have each issue for each task in the milestone. Each issue in the milestone will have their own issues. Because I want to break things down to smaller issues in which people can easily test and review.

@minhhang107
Copy link
Collaborator

So you mean having a meta issue that contains several issues? Then are we putting both the meta and the sub issues into project board?

@minhhang107
Copy link
Collaborator

for bug report, we might add Actual behavior for detailed description of the bug

@tuanthanh2067
Copy link
Owner

@minhhang107 or we can put just sub issues into the board.

@tuanthanh2067 tuanthanh2067 moved this from To Do to In progress in Seeksi Jan 9, 2022
@oliver-pham oliver-pham self-assigned this Jan 10, 2022
@oliver-pham oliver-pham added documentation Improvements or additions to documentation and removed question Further information is requested labels Jan 11, 2022
oliver-pham added a commit that referenced this issue Jan 11, 2022
@oliver-pham oliver-pham added difficulty:easy Issue that takes 1 - 3 days priority:medium Issue to be done in the current sprint labels Jan 12, 2022
@minhhang107 minhhang107 moved this from In progress to Done in Seeksi Jan 14, 2022
@oliver-pham oliver-pham reopened this Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty:easy Issue that takes 1 - 3 days documentation Improvements or additions to documentation priority:medium Issue to be done in the current sprint
Projects
Seeksi
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants