You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nesting. I need the ability to create three levels of nesting tasks. For example, the biggest task is “Authentication flows”, which contains the medium ones “Sign in flow” and “Sign up flow” tasks, which contain the smallest subtasks to work with. Such an approach is simple and useful to manage a development roadmap and the features’ completion progress.
Knowledge base functionality is needed. Throughout the development process, a lot of knowledge would have to be documented. Architectural schemas, module dependencies, code style guides, cheat sheets, even new ideas, etc. While all these things are in the chat history, random Miro boards, and various Google Docs, it’s hard to maintain and find anything quickly. We, therefore, need a source of truth for all our documentation.
Native apps. I switch between devices a lot. I’m working on my laptop, then I’m reading on my tablet, and I’m texting on my phone. It would be great to have native applications so I don’t have to find a tab in the browser.
GIT Integration. Github’s integration feature is important as well. Sometimes it is necessary to find a specific commit to check the files that were changed. Through integration, tickets automatically keep commits from a branch named as the ticket number. For example, there is an APP-11 ticket. So name a branch feature/APP-11 and the commits will be automatically stored in the ticket history.
The text was updated successfully, but these errors were encountered:
Nesting. I need the ability to create three levels of nesting tasks. For example, the biggest task is “Authentication flows”, which contains the medium ones “Sign in flow” and “Sign up flow” tasks, which contain the smallest subtasks to work with. Such an approach is simple and useful to manage a development roadmap and the features’ completion progress.
Knowledge base functionality is needed. Throughout the development process, a lot of knowledge would have to be documented. Architectural schemas, module dependencies, code style guides, cheat sheets, even new ideas, etc. While all these things are in the chat history, random Miro boards, and various Google Docs, it’s hard to maintain and find anything quickly. We, therefore, need a source of truth for all our documentation.
Native apps. I switch between devices a lot. I’m working on my laptop, then I’m reading on my tablet, and I’m texting on my phone. It would be great to have native applications so I don’t have to find a tab in the browser.
GIT Integration. Github’s integration feature is important as well. Sometimes it is necessary to find a specific commit to check the files that were changed. Through integration, tickets automatically keep commits from a branch named as the ticket number. For example, there is an APP-11 ticket. So name a branch feature/APP-11 and the commits will be automatically stored in the ticket history.
The text was updated successfully, but these errors were encountered: