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

Designing and Creating GitHub Issue Labels #7

Closed
halisbal opened this issue Mar 6, 2023 · 5 comments
Closed

Designing and Creating GitHub Issue Labels #7

halisbal opened this issue Mar 6, 2023 · 5 comments
Assignees
Labels
Priority: Medium Issues that are important but not critical, and can be worked on after higher priority issues. Status: Done Issues that have been completed. Type: Design Issues related to the design or layout of the project.

Comments

@halisbal
Copy link
Contributor

halisbal commented Mar 6, 2023

As we work together using GitHub issues, we need a clear way to organize and track our work. To achieve this, we have decided on a set of labels that we can use to better manage our issues in our meeting #1.

Here are the labels we have thought so far:

Status Labels

  • Assigned
  • In Progress
  • In Review
  • Done
  • Canceled

These labels are meant to indicate the current state of an issue. When an issue is created, it will initially be assigned the "Assigned" label. As work begins, the issue can be moved to "In Progress" and then "In Review" as it gets closer to completion. Once the issue is finished, it will be labeled as "Done". If the issue is no longer needed or is deemed unnecessary, it will be labeled as "Canceled".

Type Labels

  • Research
  • Design
  • Discussion
  • Enhancement
  • Bug
  • Feature

These labels are meant to categorize the issue based on its content. For example, if an issue is related to a bug in our project, it will be labeled as "Bug". If it's related to a new feature we want to add, it will be labeled as "Feature". If it's a discussion about a new idea or a team meeting, it will be labeled as "Discussion".

Priority Labels

  • Low
  • Medium
  • High
  • Critical

These labels are meant to indicate the level of importance of an issue. Issues labeled as "Critical" should be the top priority and require immediate attention. Issues labeled as "Low" can be addressed later when there is time.

I would like to invite our team members to share their ideas and feedback about these labels. Do you think there are any labels missing or anything that could be improved? Please let me know your thoughts.

@halisbal halisbal added Priority: Medium Issues that are important but not critical, and can be worked on after higher priority issues. Type: Design Issues related to the design or layout of the project. Status: Assigned Issues that have been assigned to someone to work on. labels Mar 6, 2023
@halisbal halisbal self-assigned this Mar 6, 2023
@halisbal halisbal added Status: In Progress Issues that are currently being worked on. and removed Status: Assigned Issues that have been assigned to someone to work on. labels Mar 6, 2023
@cisel-zumbul
Copy link
Contributor

I think it may be a good idea to add Status: New tag for the issues that is not assigned to anyone yet. Also "Help Needed" tag would be useful to quickly take action if someone gets stuck on a task.

@halisbal
Copy link
Contributor Author

halisbal commented Mar 6, 2023

I think it may be a good idea to add Status: New tag for the issues that is not assigned to anyone yet. Also "Help Needed" tag would be useful to quickly take action if someone gets stuck on a task.

Great suggestion, @cisel-zumbul
Thank you for taking the time to provide your feedback and for suggesting these additional labels. I agree that a "Status: New" label will be helpful to identify issues that are not assigned to anyone yet, and a "Status: Help Needed" label will help team members quickly identify tasks where assistance is required. I have added both labels to our repository.

@UnalDeniz
Copy link
Contributor

Another tag like Type: Documentation could also be added. Currently for wiki pages we are using Type: Design and that could cause some misunderstandings when software design issues are opened.

@halisbal
Copy link
Contributor Author

halisbal commented Mar 6, 2023

Another tag like Type: Documentation could also be added. Currently for wiki pages we are using Type: Design and that could cause some misunderstandings when software design issues are opened.

@UnalDeniz Thank you for your suggestion to add Type: Documentation as an issue label. I think it's a great idea, added it to our repository. This will help to avoid any confusion when opening software design issues.

@halisbal halisbal added Status: In Review Issues that are waiting for review and approval from others. Status: Done Issues that have been completed. and removed Status: In Progress Issues that are currently being worked on. Status: In Review Issues that are waiting for review and approval from others. labels Mar 6, 2023
@halisbal
Copy link
Contributor Author

halisbal commented Mar 6, 2023

We have decided on the current issue labels as a team. That is why I am closing this issue.

@halisbal halisbal closed this as completed Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium Issues that are important but not critical, and can be worked on after higher priority issues. Status: Done Issues that have been completed. Type: Design Issues related to the design or layout of the project.
Projects
None yet
Development

No branches or pull requests

3 participants