There should be a small module in the top right corner that shows the members you are waiting on in planning poker so that you know what hasnt answered yet.
The current way is; Click the view members button on one product in the product widget in the Home page -> Click the add member button. -> ??
We need to make a component that let you specify a user (by email?) which then sends an invite to that user.
There's some error when you try to add new milestone and label that documentPath cant be empty-string. (Also might have to handle milestone without end date).
And need to fix the if's that say "!InternalSprint" where it should be "InternalSprint", also make it lowecase.
Also add external id and external type to sprints (milestones) that get added from Github.
Add button to connect backlog to github or gitlab repo and add tag to the issues from github/gitlab such that you know which are sourced and which are not.
Should we allow the webhook to add all labels from the payload from github/gitlab/etc. This is trivial if there didnt exist any labels before the repo connected through webhooks, but if they did then it can potentially add labels that dont exist on agiletoolkit. Should we check labels and make sure only existing labels can be added or should we just allow it?
Add a role system to products. The creator will be assigned role owner and everyone else will by default get role user. The owner can then give each member a new role (which should be roles in scrum, like developer, tester, etc.)
The overview page consists of a graph (where the user can choose multiple types) where it defaults to a burndown chart. And a notifications widget that shows notifications.
It should have a creation page where it's possible to have multiple retrospective boards that are connected to a sprint (or none at all if wanted) and other options too probably. And an actual board page with lists, posts etc.
Animations for things such as closing or opening the sidebar, clicking a button and then showing a loading animation while the action is being performed, etc.
Issue editing and sprint editing should be done in realtime, such that members can collaborate on f.ex. the initial setup of an issue during sprint planning.