Skip to content

fix typo and grammar in creating-issues.mdx #58

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
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix typo and grammar in creating-issues.mdx #58

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3945d1a
stop typo in creating-issues.mdx
nekochanoide Mar 12, 2025
3b82d21
fix grammar in creating-issues.mdx
nekochanoide Mar 12, 2025
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
4 changes: 2 additions & 2 deletions src/content/docs/task-tracking/creating-issues.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Issues represent specific tasks that need to be completed. Issues can be broken

Select the Tracker view by clicking the checkbox icon on the left sidebar, and ensure the side panel is open by clicking the horizontal lines at the top left.

Click the blue `+ New issue` button at the stop of the side panel. This will open a dialog where you can enter some initial settings for your issue. After entering your desired settings, click `Create issue`.
Click the blue `+ New issue` button at the top of the side panel. This will open a dialog where you can enter some initial settings for your issue. After entering your desired settings, click `Create issue`.

> **Note:** If you navigate away while creating an issue, you'll notice that the `+ New issue` button becomes `+ Resume draft`. Click this to re-open the issue you were working on.

Expand Down Expand Up @@ -55,7 +55,7 @@ There are so many ways to customize issues to suit the needs of your specific pr

- Issues should be small in scope, representing a task assigned to just one person. For larger tasks, use sub-issues to break them down further.
- Unless they are in backlog, all new issues should have a status of "Todo" to trigger the system to create an [action item](/task-tracking/creating-action-items) for the assigned team member.
- In keeping with best practices, an issue status should not need to be manually changed from "Todo" to "In Progress" or "Done". The status of an issue can be automatically be determined by the assigned team member's action item status. For more on how this process is automated (and why), read more about action items (previously called "todos") <a href="https://huly.io/blog/capturing-dynamic-team-workflows-with-action-items" target="_blank">here</a>.
- In keeping with best practices, an issue status should not need to be manually changed from "Todo" to "In Progress" or "Done". The status of an issue can automatically be determined by the assigned team member's action item status. For more on how this process is automated (and why), read more about action items (previously called "todos") <a href="https://huly.io/blog/capturing-dynamic-team-workflows-with-action-items" target="_blank">here</a>.

## Dive deeper with our video tutorial

Expand Down