# Kanban Board (JIRA)
# The board
We have one single Kanban board (opens new window). The Board contains of several parts:
- Filters. You can leave only your cards on the board. Removing filter, you'll get a full picture on what we all are working on.
Not Readyshows what tasks we scheduled to do.
In Progressshows what we're working on right now.
Readyfor things that are ready to deploy or just not confirmed.
Doneshows what we did.
Jira keeps cards for 2 days in a
Done column, then the cards move to
# Working on a Story
- Push a card from Story Map to Jira.
- If the Story is about adding new feature or making significant change, it's recommended to write a RFC first.
- Decompose Story to sub-tasks. If Story is very simple, you can skip that step.
- Move Story to
We name our git branches by Story ID. For example,
- Keep sub-tasks small.
- You can add sub-tasks at any moment.
# Before moving Story to Ready state
- Create a Merge-Request if needed.
- Perform a demo of the changes for CS and DEV teams.
# Before moving the Story to Done state
If it's a dev Story:
- Make sure the code is merged to an upstream and the feature is deployed.
For other stories:
- Ask yourself if something else is needed. If not, move it Done.
# BUG task
If the bug blocks customers work, we fix them right away. If not, we postpone them until the next Bug Day
# SUPPORT tasks
These tasks are intended to be solved ASAP.
# How to create SUPPORT task
- Click "Create" on the navigation bar or enter
/jira createin any slack channel.
- Write an issue summary. Be precise on what's happened.
- Write a description. Try to describe how to reproduce the problem.
- Copy CarrotQuest link.
- Leave Assignee field empty, unless you know who's going to take that task.
Every morning we publish a digest with all open SUPPORT tasks. These tasks have the highest priority.