# Navigating Feedback Feed Tabs

The Ideas & Issues dashboard provides five distinct tabs to view and organize feedback. Each tab uses different sorting algorithms to surface the most relevant items based on your current needs - whether you're looking for the latest submissions, trending ideas, all-time favorites, active discussions, or items in development.

---

## The Five Feed Tabs

### 1. New Tab

**Purpose:** See the most recently submitted feedback

**Sorting Algorithm:**
```
ORDER BY created_at DESC
```

**What you see:**
- Feedback items sorted by submission date
- Newest items appear first
- Includes both ideas and issues
- No minimum vote or comment threshold

**Tab Description:** "Most recently posted"

**Best for:**
- Daily triage and review
- Catching new submissions quickly
- First response to customers
- Identifying emerging trends early

**Use Cases:**

**Morning Triage:**
```
1. Open "New" tab
2. Review items from last 24 hours
3. Assign categories and statuses
4. Respond to urgent issues
5. Link high-priority items to backlog
```

**Customer Service:**
- Respond to new issues within SLA
- Acknowledge new idea submissions
- Identify duplicate submissions
- Escalate critical bugs

**Trend Spotting:**
- Notice multiple users reporting same issue
- Identify sudden spike in specific topic
- Catch product launch feedback
- Monitor feature release reactions

**Example View:**
```
[New] Performance issue on mobile app - 2 minutes ago
[New] Feature request: Dark mode - 15 minutes ago  
[New] Bug: Export not working - 1 hour ago
[New] Idea: Bulk edit functionality - 3 hours ago
```

---

### 2. Rising Tab

**Purpose:** Discover feedback gaining momentum recently

**Sorting Algorithm:**
```
Items that have received votes in recent time period
Weighted by recency and velocity
```

**What you see:**
- Items trending upward in votes
- Recent submissions with early traction
- Ideas gaining community support
- Issues affecting multiple users

**Tab Description:** "Trending recently"

**Best for:**
- Identifying emerging priorities
- Catching issues before they escalate
- Finding ideas with growing support
- Understanding current user concerns

**Rising Algorithm Characteristics:**

**Time Window:** Typically last 7-30 days

**Factors:**
1. **Vote Velocity:** Rate of new votes
2. **Recency:** When votes were cast
3. **Acceleration:** Increasing vote rate

**Example Calculation:**
```
Rising Score = (Recent Votes / Days Since Created) × Recency Weight

Item A: 20 votes in 3 days = 6.67 votes/day
Item B: 50 votes in 30 days = 1.67 votes/day

Item A ranks higher (rising faster)
```

**Use Cases:**

**Weekly Planning:**
- Review rising items for roadmap consideration
- Identify issues needing immediate attention
- Spot feature requests gaining traction
- Prioritize based on momentum

**Proactive Response:**
- Address rising issues before they become critical
- Engage with trending idea authors
- Provide updates on popular requests
- Prevent escalation of problems

**Community Engagement:**
- Highlight rising items in newsletters
- Feature trending ideas in product updates
- Encourage voting on rising items
- Build excitement around popular requests

**Example View:**
```
[Rising] API rate limits too restrictive - 15 votes (↑ 12 this week)
[Rising] Mobile app crashes on iOS 16 - 23 votes (↑ 18 this week)
[Rising] Request: Slack integration - 31 votes (↑ 25 this week)
```

---

### 3. Top Tab

**Purpose:** View all-time most popular feedback

**Sorting Algorithm:**
```
ORDER BY total_votes DESC
```

**What you see:**
- Highest voted items ever
- Long-standing popular requests
- Community favorites
- Validated pain points

**Tab Description:** "All-time highest voted"

**Best for:**
- Strategic roadmap planning
- Understanding core user needs
- Identifying must-have features
- Validating product direction

**Vote Counting:**
```
Total Votes = COUNT of all votes WHERE:
  - feedback_item_id = item.id
  - No time restriction
  - Includes all active votes
```

**Use Cases:**

**Roadmap Planning:**
- Prioritize features with proven demand
- Validate strategic initiatives
- Justify resource allocation
- Align team on priorities

**Stakeholder Communication:**
- Show leadership what customers want most
- Demonstrate customer-driven development
- Support business case for features
- Report on customer sentiment

**Product Strategy:**
- Identify gaps in current offering
- Understand competitive weaknesses
- Validate market fit
- Guide long-term vision

**Example View:**
```
[Top] Dark mode support - 342 votes
[Top] Advanced filtering options - 287 votes
[Top] Mobile app for Android - 256 votes
[Top] SSO/SAML authentication - 198 votes
```

**Considerations:**

**Age Bias:**
- Older items have more time to accumulate votes
- May not reflect current priorities
- Balance with Rising tab for recent trends

**Validation:**
- High votes = proven demand
- Use for confident investment decisions
- Cross-reference with business metrics

---

### 4. Discussed Tab

**Purpose:** Find items with active conversations

**Sorting Algorithm:**
```
ORDER BY comment_count DESC
```

**What you see:**
- Items with most comments
- Active discussions
- Controversial or complex topics
- Items needing clarification

**Tab Description:** "Most discussed"

**Best for:**
- Understanding nuanced feedback
- Identifying complex requirements
- Engaging in active conversations
- Resolving controversial topics

**Comment Counting:**
```
Comment Count = COUNT of comments WHERE:
  - feedback_item_id = item.id
  - comment.status = 'active'
  - Includes all user and team comments
```

**Use Cases:**

**Requirements Gathering:**
- Read detailed discussions for context
- Understand edge cases and scenarios
- Gather implementation ideas from community
- Identify technical constraints

**Controversy Management:**
- Address disagreements in comments
- Provide official position on debated topics
- Moderate discussions
- Build consensus

**Community Engagement:**
- Participate in active discussions
- Answer questions from community
- Provide updates on discussed items
- Foster collaborative problem-solving

**Example View:**
```
[Discussed] Pricing model changes - 45 comments
[Discussed] Data export format options - 38 comments
[Discussed] Feature: Custom workflows - 32 comments
[Discussed] Performance optimization ideas - 28 comments
```

**Interpretation:**

**High Comments, High Votes:**
- Important, complex topic
- Strong community interest
- Requires thorough planning

**High Comments, Low Votes:**
- Controversial or niche
- May need clarification
- Could be contentious

**Low Comments, High Votes:**
- Clear, straightforward request
- Broad agreement
- Ready for implementation

---

### 5. Backlog Tab

**Purpose:** View feedback linked to development work

**Sorting Algorithm:**
```
FILTER WHERE work_item_external_id IS NOT NULL
Then apply current sort (typically New)
```

**What you see:**
- Items connected to backlog work items
- Feedback being actively addressed
- Ideas in development
- Issues being fixed

**Tab Description:** "Items currently in progress"

**Best for:**
- Tracking implementation progress
- Communicating with customers
- Monitoring development alignment
- Reporting on feedback closure

**Linking Criteria:**
```
Item is in Backlog if:
  work_item_internal_id IS NOT NULL OR
  work_item_external_id IS NOT NULL
```

**Integration Points:**
- Jira issues/stories
- Internal backlog items
- Azure DevOps work items
- Other project management tools

**Use Cases:**

**Customer Communication:**
```
1. Filter to backlog items
2. Identify items from specific customer
3. Provide status update
4. Share expected delivery timeline
```

**Development Tracking:**
- Monitor how much feedback is being addressed
- Ensure high-priority items are linked
- Track feedback-to-feature pipeline
- Measure responsiveness to customers

**Reporting:**
- Show stakeholders feedback being acted on
- Demonstrate customer-driven development
- Calculate feedback closure rate
- Measure time from submission to implementation

**Example View:**
```
[Backlog] Dark mode - Linked to JIRA-1234 (In Progress)
[Backlog] Export bug fix - Linked to JIRA-1256 (In Review)
[Backlog] API improvements - Linked to EPIC-45 (Planned)
```

**Backlog Count:**

Displayed in tab badge:
```
Backlog Count = COUNT of items WHERE:
  - work_item_external_id IS NOT NULL
  - Applies current filters
```

**Linking Best Practices:**
- Link items when work begins (not just planned)
- Update link status as work progresses
- Unlink if work is cancelled
- Use consistent linking workflow

---

## Tab Navigation

### Switching Between Tabs

**Click any tab to:**
- Change the sorting/filtering
- Update the feed instantly
- Maintain other filters (categories, status, etc.)
- Reset search (if applicable)

**Tab State:**
- Active tab highlighted
- Tab description updates
- Item count may change
- Feed refreshes automatically

### Combining Tabs with Filters

**Filters apply across all tabs:**
- Category filters
- Status filters
- Date range filters
- Type filters (Ideas vs Issues)
- Search terms

**Example Workflow:**
```
1. Select "Rising" tab
2. Filter by "Bug" category
3. Filter by "Last 7 days"
Result: Rising bugs from the past week
```

---

## Tab Selection Strategy

### Daily Workflow

**Morning:**
1. **New** - Triage overnight submissions
2. **Rising** - Check for emerging issues
3. **Discussed** - Respond to active conversations

**Weekly:**
1. **Top** - Review for roadmap planning
2. **Backlog** - Update linked items status
3. **Rising** - Identify trends for team meeting

**Monthly:**
1. **Top** - Strategic planning session
2. **Backlog** - Calculate closure metrics
3. **All tabs** - Comprehensive review

### By Role

**Customer Support:**
- Primary: **New** (respond quickly)
- Secondary: **Rising** (proactive outreach)
- Occasional: **Discussed** (complex issues)

**Product Manager:**
- Primary: **Top** (roadmap planning)
- Secondary: **Rising** (trend analysis)
- Regular: **Backlog** (tracking implementation)

**Engineering Lead:**
- Primary: **Backlog** (development tracking)
- Secondary: **Discussed** (technical details)
- Occasional: **Top** (understanding priorities)

**Executive:**
- Primary: **Top** (strategic direction)
- Secondary: **Backlog** (progress reporting)
- Occasional: **Rising** (emerging trends)

---

## Understanding Tab Counts

### Count Badges

Some tabs may show counts:
```
Backlog (23)
```

**What it means:**
- Number of items matching tab criteria
- Updates when filters change
- Helps gauge volume

**Counts are calculated:**
- Real-time when tab loads
- Based on current filters
- May differ from total feedback count

---

## Advanced Tab Usage

### Combining Multiple Views

**Workflow: Comprehensive Review**
```
1. New → Identify recent submissions
2. Rising → Check if any new items are trending
3. Top → Confirm alignment with long-term priorities
4. Discussed → Engage with active conversations
5. Backlog → Verify implementation status
```

### Custom Workflows

**Bug Triage:**
```
1. New tab
2. Filter: Type = Issue
3. Filter: Status = Unprocessed
4. Review and assign
```

**Feature Planning:**
```
1. Top tab
2. Filter: Type = Idea
3. Filter: Category = Feature Request
4. Export for roadmap meeting
```

**Customer Update:**
```
1. Backlog tab
2. Filter: Account = [Customer Name]
3. Generate status report
4. Share with customer
```

---

## Tab Performance

### Loading Speed

**Factors affecting load time:**
- Number of items in feed
- Complexity of filters
- Database query performance
- Network latency

**Optimization:**
- Tabs load limited items (typically 5-10 on dashboard)
- Infinite scroll for more items
- Caching for frequently accessed data

### Refresh Behavior

**Tabs refresh when:**
- Switching between tabs
- Applying new filters
- Navigating back to dashboard
- Manual page refresh

**Data freshness:**
- Real-time on load
- May cache for brief period
- Force refresh with browser reload

---

## Troubleshooting

### Tab Not Loading

**Symptoms:** Spinner shows indefinitely

**Solutions:**
1. Check network connection
2. Refresh browser
3. Clear filters
4. Try different tab
5. Check browser console for errors

### Unexpected Results

**Symptoms:** Items don't match expected criteria

**Verification:**
1. Check active filters
2. Verify tab selection
3. Review sort order
4. Check date range filters
5. Confirm product selection

### Empty Tab

**Symptoms:** "No items" message

**Possible Causes:**
- No items match criteria (e.g., empty Backlog)
- Filters too restrictive
- No feedback submitted yet
- Data loading error

**Solutions:**
1. Clear all filters
2. Switch to "New" tab
3. Verify feedback exists
4. Check permissions

---

## Best Practices

### Tab Usage

✅ **Start with New** - Daily triage routine  
✅ **Check Rising** - Proactive issue management  
✅ **Review Top** - Strategic planning  
✅ **Monitor Discussed** - Community engagement  
✅ **Track Backlog** - Implementation progress  

### Efficiency Tips

✅ **Bookmark tabs** - Quick access to frequent views  
✅ **Use keyboard shortcuts** - Faster navigation  
✅ **Combine with filters** - Targeted views  
✅ **Set up notifications** - Stay informed  
✅ **Export data** - Offline analysis  

### Team Coordination

✅ **Assign tab ownership** - Clear responsibilities  
✅ **Share tab views** - Collaborative review  
✅ **Document workflows** - Consistent processes  
✅ **Regular check-ins** - Team alignment  

---

## Quick Reference

| Tab | Sort | Best For | Update Frequency |
|-----|------|----------|------------------|
| New | Recent first | Triage, first response | Multiple times daily |
| Rising | Vote velocity | Trend spotting | Daily |
| Top | Total votes | Strategic planning | Weekly |
| Discussed | Comment count | Deep engagement | As needed |
| Backlog | Linked items | Progress tracking | Daily/Weekly |

---

Master the tab system to efficiently navigate your feedback, stay on top of customer needs, and ensure nothing falls through the cracks. Each tab serves a specific purpose in your feedback management workflow.