Jira team activity

Team presets

Developer and QA lists are loaded from data/teams.json on the server. Add more teams there (same shape as TMS).

Team

Story point estimation

User stories are sized by complexity. The “vs SP est.” columns compare logged time to the expected hours derived from these bands (midpoints between ranges, 8h = 1 work day).

Complexity	Duration (approx.)	Story points (SP)
Very low (XS)	<4 hours	1
Low (S)	<2 days	2
Medium (M)	2–5 days	3
High (L)	5–7 days	5
Very High (XL)	7–10 days	8
Extremely high (XXL)	10+ days	Must be sliced

Developers

Team emails (one per line or comma-separated)

Start (inclusive)

End (inclusive)

Email	Completed tasks	Related bugs	Tasks story pts	Tasks time	Tasks vs SP est.	Prod bugs done	Prod bugs pts	Prod bugs time	Prod vs SP est.

QA

QA emails (one per line or comma-separated)

QA start (inclusive)

QA end (inclusive)

Email	Completed tasks	Related bugs	Tasks QA pts	Tasks QA time (h)	Tasks QA vs SP est.	Prod bugs done	Prod bugs QA pts	Prod bugs QA time (h)	Prod QA vs SP est.