- Cần có attachment và comment riêng
- Cần có status (các status nào?)
- Cần có weight
- Có cần duedate riêng không?
- Có cần được approved bởi manager?
from fastapi import FastAPI, Depends, UploadFile | |
from fastapi.responses import StreamingResponse | |
import xlsxwriter | |
import io | |
from openpyxl import load_workbook | |
from openpyxl.worksheet.worksheet import Worksheet | |
from typing import List, Dict | |
class ExcelService: |
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "The current time period don't have this employee" | |
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not the reviewer of this employee in current time period" | |
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not allowed to create comment" | |
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "Comment not found" | |
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not authorized to update this comment" | |
./app/api/admin_v2/comments.py: status.HTTP_404_NOT_FOUND, "You are not authorized to delete this comment" | |
./app/api/admin_v2/sessions.py: status.HTTP_400_BAD_REQUEST, "Time period already exists" | |
./app/api/admin_v2/sessions.py: status.HTTP_400_BAD_REQUEST, "Can't create time period for past year" | |
./app/api/admin_v2/sessions.py: status.HTTP_400_BAD_REQUEST, "Can't create time period for past quarter" | |
./app/api/admin_v2/sessions.py: status.HTTP_404_NOT_FOUND, "Time period not found" |
# against jira.atlassian.com. | |
from __future__ import annotations | |
from jira import JIRA | |
from enum import Enum | |
from typing import DefaultDict, List | |
from collections import defaultdict |
This document describes what different story points mean in practice. By design, story points are not supposed to be connected to units of time (hours, days or weeks). They are meant to be relative units which give a rough understanding of the amount of work required to complete a story. Story points between different teams, departments and companies should never be compared.
Team A delivering 100 story points in a sprint might actually be much more than Team B delivering 200 story points because the teams don’t share a standardised definition what 1 story point means. By no means is this an attempt to create such a standardisation, but to give us a guideline what to follow when estimating stories.
For all stories, the pull request still needs to be reviewed, automated tests have to pass and a new version get deployed to be able to mark it as completed. This is an overhead that should be included in all estimates. Sometimes this overhead takes much more time than completing the ac