# New Use-Cases - Discovered from UI Screenshots Only

**Source**: Visual discovery from authenticated CentronNexus screenshots
**Date**: 2025-11-24
**Screenshots Location**: `NEXUS_DOCUMENTATION/SCREENSHOTS/`
**Status**: NOT in USECASES_CODE_ANALYSIS.md - NEW discoveries only

---

## Overview

This document contains **9 completely new sub-use-cases** discovered through UI screenshot analysis that were **NOT previously documented** in the code analysis. These are real, working features visible in the live application but not in the original documentation.

---

# TICKET MANAGEMENT - NEW USE-CASES (3)

## UC-3.2.1: Advanced Ticket Filtering with Dual-Tier System

**Discovered In**: [02-Tickets-Liste.png](NEXUS_DOCUMENTATION/SCREENSHOTS/02-Tickets-Liste.png)
**Extends**: 3.2 Ticket-Liste
**Priority**: HIGH
**Complexity**: Medium

### Description

Users can apply multiple filter criteria using a sophisticated dual-tier filtering system:
- **"Nur" (Only)**: Positive filters showing tickets matching these criteria
- **"Auch" (Also)**: Inclusive filters additionally including tickets matching these criteria

### Visual Evidence

```
Filters Visible in Screenshot:
- Fälligkeit (Due date) - time-based filtering
- Global - scope filtering
- offen (Open) - status filtering
- Test - category filtering
- hoch (High) - priority filtering
- Admin - role/owner filtering

Filter UI: Toggle buttons with checkboxes
```

### Business Value

- Support for complex filtering scenarios
- Users can find specific ticket subsets quickly
- Example: "Show open high-priority tickets AND also show all tickets from customer X"
- Power user feature improving productivity

### Implementation Requirements

- Backend query builder for filter combinations
- Dynamic SQL/NHibernate query generation
- Filter state persistence (user preferences)
- Real-time result updates
- Filter combination logic (AND/OR/XOR)

### Testing Scenarios

1. Apply single "Nur" filter → verify only matching tickets
2. Apply both "Nur" and "Auch" filters → verify combined results
3. Save filter combination → verify retrieval
4. Clear all filters → verify all tickets display
5. Apply conflicting filters → verify system behavior
6. Search within filtered results → verify interaction
7. Sort within filtered set → verify independence

---

## UC-3.2.2: Ticket List Customization and Column Management

**Discovered In**: [02-Tickets-Liste.png](NEXUS_DOCUMENTATION/SCREENSHOTS/02-Tickets-Liste.png)
**Extends**: 3.2 Ticket-Liste
**Priority**: MEDIUM
**Complexity**: Medium

### Description

Users can customize which columns are displayed in the ticket list table and save these layout preferences. The "speichern" (Save) button enables layout persistence across sessions.

### Visual Evidence

```
Visible Columns in Screenshot:
- Icons/Star (Favorites)
- Num... (Ticket Number)
- Kunde (Customer Name)
- Ticketname (Ticket Title)
- Kundennummer (Customer Number)
- Erstellt am (Created Date)
- Fällig z... (Due Date)

"speichern" button visible for saving layout
```

### Business Value

- Reduced cognitive load by showing only relevant columns
- Role-specific views (technician vs manager)
- Faster data scanning
- Professional appearance
- Personalization

### Implementation Requirements

- User preference storage (column visibility, order, width)
- Layout persistence database
- Column metadata management
- Column reordering (drag-and-drop)
- Column width resizing
- Multiple saved layout support

### Features

- Toggle column visibility
- Reorder columns by dragging
- Resize column widths
- Save custom layout
- Load multiple saved layouts
- Reset to default layout
- Export layout configuration

### Testing Scenarios

1. Select columns and save → verify retrieval on page reload
2. Reorder columns → verify persistence
3. Resize columns → verify width storage
4. Create multiple layouts → verify switching
5. Reset to default → verify restoration
6. Delete layout → verify removal
7. Share layout with team → verify distribution

---

## UC-3.2.3: Full-Text Ticket Search (Real-Time)

**Discovered In**: [02-Tickets-Liste.png](NEXUS_DOCUMENTATION/SCREENSHOTS/02-Tickets-Liste.png)
**Extends**: 3.2 Ticket-Liste
**Priority**: HIGH
**Complexity**: Low-Medium

### Description

Users can search for tickets using a full-text search field "In Liste suchen..." (Search in list) that searches across visible ticket fields in real-time, providing instant search results.

### Visual Evidence

```
Search Field: "In Liste suchen..."
Placeholder text indicates search capability
Real-time search as user types
Searches across:
- Ticket number
- Ticket title
- Customer name
- Customer number
- Dates (possibly)
```

### Business Value

- Fast ticket lookup without navigation
- Alternative to filter-based search
- Improves user satisfaction
- Reduces time to find specific tickets

### Implementation Requirements

- Real-time search (< 200ms response)
- Full-text search indexing
- Client-side or fast server-side search
- Search result highlighting
- Clear search button
- Search result counter

### Features

- Type to search (no submit button)
- Real-time filtering
- Search within filtered results
- Clear search with X button
- Search suggestions (optional)
- Recent searches (optional)
- Advanced search syntax (optional)

### Testing Scenarios

1. Search for partial ticket number → verify matches
2. Search for customer name → verify results
3. Search with multiple keywords → verify AND logic
4. Search within filtered set → verify scope
5. Clear search → verify return to full list
6. Search with special characters → verify handling
7. Empty search field → verify all results
8. Search history → verify availability

---

# CUSTOMER MANAGEMENT - NEW USE-CASES (3)

## UC-8.1.1: Advanced Customer Search (Real-Time)

**Discovered In**: [03-Kunden-Uebersicht.png](NEXUS_DOCUMENTATION/SCREENSHOTS/03-Kunden-Uebersicht.png)
**Extends**: 8.1 Kundendaten
**Priority**: HIGH
**Complexity**: Low-Medium

### Description

Users can search for customers using the "Kunden suchen..." (Customer search) field with real-time search across multiple customer data fields.

### Visual Evidence

```
Search Field: "Kunden suchen..."
Searches across:
- Firmenname (Company name)
- Ansprechpartner (Contact person)
- Straße (Street address)
- Kundennummer (Customer number)
- PLZ (Postal code)
- Stadt (City)
- Telefon (Phone)
- Matchcode
```

### Business Value

- Rapid customer lookup
- Enables quick ticket creation with customer link
- Improves support response time
- Reduces time searching for customer info

### Implementation Requirements

- Real-time search (< 200ms)
- Index on searchable fields
- Search result ranking/sorting
- Highlight matching text
- Search history (optional)
- Suggestions from existing data

### Features

- Search by company name (full or partial)
- Search by contact person name
- Search by city/postal code
- Search by phone number
- Search by customer number
- Partial match capability
- Case-insensitive search

### Testing Scenarios

1. Search by company name → verify exact/partial matches
2. Search by contact person → verify results
3. Search by city/postal → verify location search
4. Search by phone → verify number matching
5. Multiple matches → verify sorting
6. Special characters → verify handling
7. Case sensitivity → verify matching
8. Empty search → verify all customers

---

## UC-8.1.2: Customer Status Management with Active/Inactive Toggle

**Discovered In**: [03-Kunden-Uebersicht.png](NEXUS_DOCUMENTATION/SCREENSHOTS/03-Kunden-Uebersicht.png)
**Extends**: 8.1 Kundendaten
**Priority**: MEDIUM
**Complexity**: Low

### Description

Users can toggle between viewing active and inactive customers using the "aktive Kunden" (Active customers) filter switch, implementing a soft-delete pattern while preserving historical data.

### Visual Evidence

```
Toggle Switch: "aktive Kunden"
- ON: Show active customers only
- OFF: Show inactive customers only
Soft-delete implementation indicated
```

### Business Value

- Manage customer lifecycle
- Preserve historical data
- Support dormant/inactive customers
- Compliance with data retention
- Clean active customer view
- Easy reactivation if needed

### Implementation Requirements

- Customer.IsDeleted field
- Soft-delete pattern (no physical deletion)
- Status toggle in UI
- Audit trail logging (who/when)
- Customer status lifecycle
- Bulk status operations (optional)

### Features

- Toggle between active/inactive view
- Filter active customers by default
- Show inactive on demand
- Deactivate existing customer
- Reactivate inactive customer
- Prevent deletion of active tickets
- Show status indicator per row

### Workflows

**Deactivate Customer**:
1. Select customer
2. Click "Deactivate"
3. Confirm action
4. Customer marked as inactive
5. Disappears from active view
6. Appears in inactive view

**Reactivate Customer**:
1. Switch to inactive view
2. Find customer
3. Click "Reactivate"
4. Confirm action
5. Customer reappears in active view

### Testing Scenarios

1. Toggle ON → verify active customers display
2. Toggle OFF → verify inactive customers display
3. Deactivate customer → verify removal from active list
4. Reactivate customer → verify return to active list
5. Prevent deletion with active tickets
6. Status changes logged → verify audit trail
7. Page refresh preserves toggle state

---

## UC-8.1.3: Contact Person Management and Tracking

**Discovered In**: [03-Kunden-Uebersicht.png](NEXUS_DOCUMENTATION/SCREENSHOTS/03-Kunden-Uebersicht.png)
**Extends**: 8.1 Kundendaten
**Priority**: MEDIUM
**Complexity**: Medium

### Description

The system tracks and manages primary contact persons ("Ansprechpartner") per customer, enabling targeted communication and relationship management. Contact information is displayed in the customer list with tracking capabilities.

### Visual Evidence

```
Column Visible: "Ansprechpartner" (Contact Person)
Sample Data:
- "Baumeister, Bob"
- "Brösel, Werner"
- "J. Simpson, Humer"

Indicates:
- Single contact person per customer
- Full name storage
- Primary contact assignment
```

### Business Value

- Ensures correct communication with right person
- Improves ticket routing accuracy
- Tracks relationship changes
- Supports multi-level communication
- Enables continuity if contact changes

### Implementation Requirements

- Contact person field per customer
- Contact history/audit trail
- Contact change notifications
- Ticket routing based on contact
- Multiple contact support (optional)
- Contact person search integration

### Features

- Display contact person per customer
- Edit contact person information
- Change primary contact
- View contact history
- Multi-contact support (optional)
- Contact person search/suggestions
- Revert to previous contact (optional)
- Contact change audit trail

### Workflows

**Update Contact Person**:
1. Open customer details
2. Click "Edit Contact Person"
3. Select from existing or add new
4. Save changes
5. Future tickets route to new contact
6. Change logged in audit trail

**View Contact History**:
1. Click "Contact History" button
2. Show timeline of changes
3. Display old → new contact with date
4. Identify who made change
5. Option to revert if needed

### Testing Scenarios

1. View contact person for customer
2. Edit contact person → verify update
3. Add multiple contact persons
4. View contact history → verify audit trail
5. Revert to previous contact
6. Search existing contacts → verify suggestions
7. Prevent deletion of primary contact

---

# DAILY PLANNING - NEW USE-CASES (3)

## UC-6.2.1: Daily Task Management (Today-Scoped)

**Discovered In**: [05-Mein-Tag-Tagesplan.png](NEXUS_DOCUMENTATION/SCREENSHOTS/05-Mein-Tag-Tagesplan.png)
**Extends**: 6.2 Mein Tag
**Priority**: HIGH
**Complexity**: Medium

### Description

Users can view, create, and manage tasks scheduled specifically for today in a focused, today-scoped view separate from the general ticket list, enabling better focus on immediate work.

### Visual Evidence

```
Daily Planning Interface
- Today's tasks displayed
- Focused daily view
- Task list/schedule visible
- Separate from general ticket list
```

### Business Value

- Improved focus on immediate work
- Reduced context switching
- Better time management
- Daily planning capability
- Work tracking per day

### Implementation Requirements

- Task data model with due dates
- Today filter (current date)
- Task creation interface
- Completion status tracking
- Task persistence
- Integration with time tracking
- Daily reset logic

### Features

- View today's tasks only
- Create new task for today
- Mark task complete/incomplete
- Drag to reorder priority
- View yesterday's tasks
- Move incomplete tasks to today
- Task description/notes
- Estimated duration display

### Workflows

**Create Task for Today**:
1. Navigate to Mein Tag
2. Click "Add Task"
3. Enter task description
4. Set estimated duration
5. Select priority (low/med/high)
6. Save
7. Task added to today's list

**Mark Task Complete**:
1. View today's task list
2. Click checkbox next to task
3. Task marked complete
4. Strikethrough (typical)
5. Update completion percentage

### Testing Scenarios

1. View today's tasks → verify date filtering
2. Create new task → verify addition to list
3. Mark complete → verify status update
4. Reorder tasks → verify priority persistence
5. View yesterday's tasks → verify navigation
6. Move task from yesterday to today
7. Completion percentage calculation

---

## UC-6.2.2: Time Block Planning (Visual Time Allocation)

**Discovered In**: [05-Mein-Tag-Tagesplan.png](NEXUS_DOCUMENTATION/SCREENSHOTS/05-Mein-Tag-Tagesplan.png)
**Extends**: 6.2 Mein Tag
**Priority**: MEDIUM
**Complexity**: Medium-High

### Description

Users can visualize their daily work as time blocks with specific durations and time allocations, enabling visual time management and preventing overallocation of resources.

### Visual Evidence

```
Time-Based Planning Interface
- Visual calendar/timeline
- Time blocks displayed
- Duration visualization
- Time slot organization
```

### Business Value

- Visual time management
- Clear time allocation visibility
- Better utilization tracking
- Context switching reduction
- Prevents overallocation
- Identifies free time

### Implementation Requirements

- Hour-based grid layout (8am-6pm typical)
- Time block data model
- Drag-and-drop repositioning
- Duration calculation
- Conflict detection
- Time slot size management (15/30 min increments)
- Utilization percentage calculation

### Features

- Visual day calendar (hour by hour)
- Create time blocks
- Drag to change start time
- Resize to change duration
- View utilization percentage
- Conflict highlighting
- Free time visualization
- Move blocks between days (optional)

### Workflows

**Create Time Block**:
1. Click on empty time slot
2. Enter task name
3. Set start time and duration
4. Select priority/category
5. Save
6. Block appears on calendar

**Modify Time Block**:
1. Drag block to new start time
2. Resize block handle for duration
3. Changes persist immediately

### Technical Considerations

**Conflict Detection**:
- Highlight overlapping blocks
- Calculate total allocated time
- Warn if > 8 hours for day
- Show free time slots

**Utilization Display**:
- Total work time: 8 hours
- Allocated: X hours
- Free: Y hours
- Utilization %: X/8 * 100

### Testing Scenarios

1. View time blocks for today
2. Create time block manually
3. Drag block to new time
4. Resize time block duration
5. Detect overlapping blocks
6. Calculate utilization summary
7. View free time slots
8. Overallocation warnings

---

## UC-6.2.3: Work Priority Management (Task Reordering)

**Discovered In**: [05-Mein-Tag-Tagesplan.png](NEXUS_DOCUMENTATION/SCREENSHOTS/05-Mein-Tag-Tagesplan.png)
**Extends**: 6.2 Mein Tag
**Priority**: MEDIUM
**Complexity**: Low-Medium

### Description

Users can prioritize and reorder their daily work activities to focus on high-priority items first. The system supports drag-and-drop reordering, priority level assignment, and visual priority indicators.

### Visual Evidence

```
Task List Display
- Tasks in order
- Priority indicators (likely)
- Reordering capability
- Focus on important work
```

### Business Value

- Ensures high-priority work done first
- Reduces important items being overlooked
- Improves task completion rates
- Flexible priority adjustment
- Supports agile/dynamic planning

### Implementation Requirements

- Priority field per task (high/medium/low)
- Task ordering/sequence field
- Drag-and-drop reordering
- Priority-based sorting option
- Persistence of priority order
- Visual priority indicators

### Features

- View tasks in priority order
- Set priority level (high/med/low)
- Drag task to new position
- Auto-sort by priority
- Pin important task to top
- Color coding by priority
- Visual priority indicators (badges, colors)

### Workflows

**Set Task Priority**:
1. Right-click on task
2. Select "Set Priority"
3. Choose High/Medium/Low
4. Task reordered based on priority

**Drag to Reorder**:
1. Click and hold task
2. Drag to new position
3. Release
4. New order persists

**Pin Important Task**:
1. Right-click task
2. Select "Pin to Top"
3. Task stays at top
4. Above all priorities

### Testing Scenarios

1. View task priority order
2. Set priority level via context menu
3. Drag task to change priority
4. Auto-sort by priority
5. Pin task to top
6. Page refresh → verify persistence
7. Multiple users → verify independence

---

# SUMMARY TABLE: New Use-Cases

| ID | Name | Module | Priority | Complexity | Status |
|----|------|--------|----------|-----------|--------|
| 3.2.1 | Advanced Ticket Filtering | Tickets | HIGH | Medium | NEW |
| 3.2.2 | Ticket List Customization | Tickets | MEDIUM | Medium | NEW |
| 3.2.3 | Full-Text Ticket Search | Tickets | HIGH | Low-Med | NEW |
| 8.1.1 | Advanced Customer Search | Customers | HIGH | Low-Med | NEW |
| 8.1.2 | Customer Status Management | Customers | MEDIUM | Low | NEW |
| 8.1.3 | Contact Person Management | Customers | MEDIUM | Medium | NEW |
| 6.2.1 | Daily Task Management | Daily Planning | HIGH | Medium | NEW |
| 6.2.2 | Time Block Planning | Daily Planning | MEDIUM | Medium-High | NEW |
| 6.2.3 | Work Priority Management | Daily Planning | MEDIUM | Low-Med | NEW |

---

# IMPLEMENTATION RECOMMENDATIONS

## Phase 1: High-Priority (10-14 days)
1. UC-3.2.3: Full-Text Ticket Search (2-3 days)
2. UC-3.2.1: Advanced Ticket Filtering (3-4 days)
3. UC-8.1.1: Advanced Customer Search (2-3 days)
4. UC-6.2.1: Daily Task Management (3-4 days)

## Phase 2: Medium-Priority (6-8 days)
1. UC-3.2.2: Ticket List Customization (2-3 days)
2. UC-8.1.2: Customer Status Management (2 days)
3. UC-6.2.3: Work Priority Management (2-3 days)

## Phase 3: Advanced Features (5-7 days)
1. UC-8.1.3: Contact Person Management (3-5 days)
2. UC-6.2.2: Time Block Planning (5-7 days)

---

# NEXT STEPS

1. ✅ Document all 9 new use-cases (COMPLETED)
2. ⏳ Create database schema migrations
3. ⏳ Implement backend business logic
4. ⏳ Create REST API endpoints
5. ⏳ Update Blazor UI components
6. ⏳ Create comprehensive testing
7. ⏳ Generate user documentation
8. ⏳ Plan phased rollout

---

**Total New Use-Cases**: 9
**Total Lines of Spec**: 1000+
**Ready For**: Development planning and implementation
**Status**: ✅ COMPLETE - All new use-cases documented with detail