Introduction to issues
Issues are like big to do’s. They should contain only one specific task (as any good to do item on a list). But because they might be more difficult or complex than a to do, an issue needs some more explanation. That’s why you can write as many instructions as you want. You can also attach files and leave comments to discuss the issue with colleagues.
Because issues are more complex than to do items, you can assign them to different users. Or the user, who works on the issue, might assign it to his colleague for review.
You can also set a deadline for the issue. This is super handy if you need something done fast or if you want to communicate that something is not so important and only needs to be completed to a very late date.
You can also add a status to each issue. Have a look at how kanban boards work below, to learn more about this feature.
To create an issue, simply press “t” on your keyboard or move your mouse or finger over the green button from within a project. From there chose the second entry with a document icon and a clock to add a issues.
To delete a issue, simply click on the “x” at the top right corner of the task card. But be aware: Deleting a task will also delete all associated comments.
Introduction to kanban boards
If you have a bigger project, you will also have a big pile of issues to be resolved. That can make it hard keeping track. That’s what the kanban board is for. You can activate the board by choosing it from the view popup below the project menu on the task overview page. Three rows will appears labeled as “To Do”, “Review” and “Done”. By default, all tasks will be within the first row “To Do”. Let’s say you have an issue assigned to you. After you completed the issue, you can re-assign it to you colleague who needs to check the result. After doing that you move the task card from the first row into the second called “Review”. Now everyone in the team can see that this task has been worked on and that it is now in “review” mode. This simple but effective way of organizing your work can save you hundreds of emails and chats. Everyone knows exactly what he has to do next and where to find the information necessary. Be aware to always re-assign the task to the person responsible for review. This will make it easy for everyone to figure out what has to be done next.
Add more rows
You can add mroe rows to your kanban board by clicking on the cogwheel icon on the right side. There are some options to be aware of:
Don’t count issues: Issues in this row won’t be counted in the counter of the tabs and menues. This is usually meant for the “Done” row. When an issue is completed, it can be put in the “Done” row, meaning there doesn’t have to be more work done on it. That’s why it shouldn’t be counted any more. However you can also use it the other way around and don’t count issues in the first row. That way the counter will only show issues that are actively worked on.
Enable trash: Adds a small trash icon to the row to quickly delete all issues within that row.
Minimal cards: Turns off the “by Author-line” and “time of last change-line” – making the issue much smaller (comes in handy if you have a lot of issues).
You’ll notice that the kanban board itself is within a container. Click on the plus icon next to it to add a another container. You can have multiple container – all with their own kanban boards. This is super handy if you have large projects and want one container for all the code related work and another for all the design related one etc.
What is the backlog?
If you don’t chose a container and kanban board when creating an issue, it will be put in the backlog. From there you can later file in into any container/kanban board you want.