velkymx / tickets Goto Github PK

I was looking into this projects in Laravel and have cloned the repository. However, I am unable to find tables structure dump?

Am I missing something?

There are two target audiences for a sprint summary document. The first is any interested outsiders. This could include the VP of development, executives, stakeholders, department management, other teams and so on.

The second audience is future versions of the agile team itself. I’ve been in many situations where a team wanted to look back in time. A sprint summary can provide that view.

https://www.mountaingoatsoftware.com/blog/summarizing-the-results-of-a-sprint

https://www.scrumdesk.com/start/manual-for-scrumdesk-start/start-sprint-report/

https://agileaxiomframework.com/sprint_summary_report.html

The milestone / sprint screen is great for managing work queues. It would be MORE great if it included a burn down chart.

1. 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.

2. 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.

3. 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.

4. 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.

Add the ability to watch any tickets in the milestone