Project Management
- CRUD Issues (archiveable)
- Fields: Title, Text, ?Parent, [Customizable Attributes]
- Markdown
- Children Issues
- Issue Types
- Custom Issue Types
- CRUD Sprints
- Fields: Name, Due, Frequency
- CRUD Boards (Kanban)
- Order/Organize Issues
- CRUD Comments (for each issue)
- Markdown
- User Roles (either per project or per team)
- Administrators manage projects
- Developers work on issues in projects
- Users create and read issues in projects
- Jira Integration
- Readonly? To encourage use from our app
- Sync comments and issues
- GitHub Integration
- Link issues and comments together (2 way sync)
- Minimum Permissions asked for
- 1-1 user to github account (people using multiple github accounts should use multiple of ours)
This project should be able to be run side by side with Jira.
It's worth noting that the complexity and vastness of features in JIRA can be overwhelming for some users, especially for smaller teams or for those who prefer a simpler, more straightforward tool.
Do we need something like JQL right off the bat? Can we get simple search done right?
Customizable reports and dashboards?
We should provide easy visibility into project status and team performance.
Simple and secure, ensure that sensitive information is only accessible to the right people.
With the above roles per project and per team, you can easily create user accounts for any type of real position. For example, stakeholders could be given read only access to what they need to focus on. Customers could be given read/write only access to their own issues. Creators/Contributors can be given read/write access to all issues in certain projects.
Integrations will naturally help this grow.
Two biggest types.
Can we make these easy and out of the box?
Which of these is most necessary? Should we focus on Git providers first/only? (GitHub, GitLab, Bitbucket)