Files

T

Nima Nakhostin 1a56070556 Add MinIO Package for Object Storage Management

- Introduced a comprehensive MinIO package for managing object storage, including support for hierarchical document storage and general file management.
- Implemented core components such as Config, ConnectionManager, and Service, following Clean Architecture principles.
- Added functionality for file uploads, downloads, bucket management, and structured logging, enhancing usability and maintainability.
- Included detailed error handling and validation for configuration and operations, ensuring robustness.
- Updated documentation with usage examples and configuration guidelines to facilitate integration and understanding of the package's functionality.

2025-11-09 09:52:09 +03:30

2.3 KiB

Raw Blame History

Jira Task Creation Rules and Standards

📋 Mandatory Rules for Creating Jira Tasks

1. Labels - REQUIRED

Always set appropriate labels based on task type:

Application tasks → application
Panel tasks → panel
Backend tasks → backend
DevOps tasks → devops
QA tasks → qa
Design tasks → design

2. Sprint Assignment - MANDATORY

ALL tasks must be assigned to the CURRENT ACTIVE SPRINT
Never assign to past or future sprints
Always check current sprint before task creation

3. Task Relationships - REQUIRED

If task has a reference → use relates to
If task is dependent → use depends on
If task is a subtask → use parent
Always link related tasks with proper relationship type

4. Team Assignment by Role

Application Developer: a.ghabeli
Panel Developer: a.jamali
Backend Developer: n.nakhostin
QA: a.sheikhmemari
Designer: s.fathali
DevOps: n.nakhostin, h.barzegar

5. Task Structure Standards

Summary: Clear, concise task title
Description: Detailed requirements and context
Acceptance Criteria: Checklist format with [ ] checkboxes
Backend Integration: Include API details if applicable
Related Tasks: Add references in comments

6. Task Types

Task: General development work
Bug: Issues and fixes
Story: User stories and features
Subtask: Child tasks under parent tasks

7. Priority Levels

Highest: Critical issues, blocking bugs
High: Important features, major bugs
Medium: Standard features, minor bugs
Low: Nice-to-have features, enhancements

8. Comments and Updates

Always add comments when linking related tasks
Include technical details and dependencies
Update task status regularly
Add progress updates in comments

🚨 CRITICAL REMINDERS

NEVER create tasks without proper labels
ALWAYS assign to current active sprint
MUST link related tasks with proper relationships
REQUIRED to include detailed acceptance criteria
MANDATORY to assign to correct team member

This document serves as the standard for all Jira task creation in the TM project. Last updated: October 9, 2025

2.3 KiB Raw Blame History