---
# System prepended metadata

title: Issues we encountered.

---

# Issues we encountered.

## Jira
- Jira is full of old card
- Card aren’t clear to understand

## Title isn't clear
![](https://i.imgur.com/R1bxOZ2.png)

### Issue
Titles are all in Chinese and not always clear to understand about code
:::success
### Solution
Every card should identify code entity by English name similar as name inside code.

Ex: Add SQL Mgmt Tabs in Root
:::


## Content of card isn't clear
### Issue
Cards don't have any description and aren't
 clear so much
:::success
### Solution
Describe every card with at least 1 US (User Story) to help understand the main goal of the Story

Additionaly, you may still use Chinese in description if it's too hard to understand.

Finally, the first line of each card's description should show the location of the feature for front.
(For example : Home > Production Report > OEE Analysis) 
:::
## Different kind of task isn't clear
### Issue 
It's hard to see every kind of task like a new feature or a bug
:::success
### Solution
We should use the 3 type of Card of Jira:
- Story: for new feature 
(Story format : as a [user] I would like [enhancement] so that I can [benefit realized]
example: As a user, I would like to add items to my cart so that I can buy them)
- Bug: for bug
- Task: for any task like an enhancement
###
Additionally, we could add labels inside the card to show more details about the type of card we are using. Like this :
- new feature
- enhancement
- bug
- request by client
- emergency
:::

## Size of task isn't shown
### Issue 
When setting up a card, we don't setup what's called "***sprint points***" in Jira, or anything related to the difficulty/size of a task. Thus we can't tell if it might take less than a day or a week.

It is also interesting to put the size of a task, to be able to evaluate how much every one can do before it's getting too much.
:::success
### Solution
We should use a system of points to define the size of a user story (It's important to notice that it shouldn't use time as a reference, to not give any pressure about a deadline, but instead work together as a team).

Here is an example :

| Tshirt size | Sprint Points |
| ----------- | ------------- |
| XS          | 0             | 
| S           | 1             | 
| M           | 2             | 
| L           | 3             | 
| XL          | 5             | 
| XXL         | 8             | 

:::

## Lifecycle
### Issue
Jira is full of old cards
:::success
### Solution
At the end of each sprint, we should filter all the remaining cards and decide wether or not to keep it.
All the overdue cards must be setup with a more do-able due date (must discuss with devs to estimate the new deadline).
:::

## We are not prioritizing work
### Issue
Too many tasks are asked to do at the same time. Thus, sometimes we focus on tasks that are not the most important.
:::success
### Solution
We should limit each Kanban column to 5 cards or so. That will force devs to learn how to prioritize their work while relieving them of any work overload.



