Bug Reports

Trying to utlitize the folders for Riftbound and they don't seem to work- when I press the "Move to folder," nothing happens, and dragging them into the folder gives me this error

## Problem Statement The deckbuilder's default card display does not align with common user workflows. Users typically want to start by adding a Legend (commander) and then choose Champions, but the initial view shows cards alphabetically (starting with "Acceptable Losses") rather than prioritizing the most relevant card types for deck-building workflows. ## Current Behavior Deckbuilder opens with cards sorted alphabetically First visible card is "Acceptable Losses" No intelligent default filtering or sorting based on deck-building patterns ## Expected Behavior The deckbuilder should provide intuitive pathways that match common deck-building workflows: Option to start with Legends/Commanders first Smart default sorting/filtering based on the format or deck type Quick access to key card types (Legends, Champions, etc.) ## User Story As a deck builder, I want the card browser to show me relevant cards for my current deck-building step, so I can build decks more efficiently without manually filtering through alphabetical lists. ## Screenshot Reference Image attached shows the current default view starting with "Acceptable Losses" ## Acceptance Criteria [ ] Investigate common deck-building workflows and starting points [ ] Implement smarter default card sorting/filtering [ ] Consider format-specific defaults (Commander starts with Legends, etc.) [ ] Provide quick-access buttons or tabs for common card types [ ] Maintain alphabetical sort as an available option

## Problem Statement There is a plus sign (+) element in the UI that appears to be non-functional or confusing. The element is visible but either cannot be clicked or its purpose is unclear. ## Current Behavior A plus sign is displayed in the interface (see attached screenshot) The element appears to be non-interactive or its interaction is unclear User expectation is that it should be clickable to add something ## Expected Behavior One of the following should be implemented: Make the plus sign clickable with a clear action (add card, add section, etc.) Remove the plus sign if it serves no purpose Add a tooltip or visual cue explaining the element's function ## Screenshot Reference Image attached shows the plus sign element in question ## Location Need to identify the specific screen/component where this plus sign appears (based on screenshot context) ## Acceptance Criteria [ ] Identify the location and purpose of the plus sign element [ ] Either make the element interactive with clear feedback, or remove it [ ] If kept, ensure proper hover states and click affordance [ ] Add tooltip if the action is not immediately obvious [ ] Test across different screen sizes to ensure consistency

## Problem Statement The filter buttons in the deckbuilder have poor UX - they are not visually obvious and exhibit buggy behavior. ## Current Issues Discoverability : Filter buttons are not visually obvious or intuitive Buggy Behavior : Buttons exhibit inconsistent or unexpected behavior (specific bugs need identification) ## Screenshot Reference Image attached shows the filter buttons in question ## Areas to Investigate Visual styling and affordance of filter buttons Active/inactive state visibility Click/toggle behavior consistency Filter state persistence Multiple filter interaction (AND/OR logic) Clear/reset functionality ## Expected Behavior Filter buttons should have clear visual styling that indicates they are interactive Active filters should be clearly distinguished from inactive ones Clicking filters should provide immediate visual feedback Filter behavior should be predictable and consistent ## Acceptance Criteria [ ] Audit current filter button styling and identify visibility issues [ ] Document specific buggy behaviors observed [ ] Improve button visual design for better affordance [ ] Add clear active/inactive states with distinct styling [ ] Fix any toggle or state management bugs [ ] Add hover states and click feedback [ ] Consider adding filter count badge or indicator [ ] Test filter combinations for logical consistency

## Problem Statement A workflow in the application requires too many clicks to complete, creating friction in the user experience. The specific workflow needs to be identified from the attached screenshot. ## Screenshot Reference Image attached shows the UI area with excessive click requirements ## Current Behavior Users must perform multiple clicks to accomplish what should be a simpler action. This creates unnecessary friction and slows down common workflows. ## Investigation Needed Based on the screenshot, identify: Which specific feature/workflow has too many clicks The current click count to complete the action Which steps could be combined or eliminated ## Potential Solutions to Explore Single-click actions where double-click is currently required Keyboard shortcuts for common actions Batch operations instead of individual item actions Contextual menus or quick actions Default selections that reduce required input Drag-and-drop alternatives ## Acceptance Criteria [ ] Identify the specific workflow from the screenshot [ ] Document current click count for the workflow [ ] Propose streamlined interaction pattern [ ] Reduce click count by at least 50% or to a maximum of 2-3 clicks [ ] Maintain discoverability of the action [ ] Test that streamlined flow is intuitive for new users

## Problem Statement The Riftbound card sorting does not default to collector number, and lacks a domain sorting option. Users expect cards to be sorted by collector number by default, with additional sorting options available. ## Screenshot Reference Image attached shows the current Riftbound sorting interface ## Current Behavior Riftbound cards are not sorted by collector number by default No option to sort by domain ## Expected Behavior Default Sort : Cards should default to sorting by collector number Domain Option : Add ability to sort/group cards by domain ## Implementation Details Change default sort order to collector number (ascending) Add "Domain" as a sorting/grouping option in the sort dropdown Maintain other existing sort options ## Acceptance Criteria [ ] Riftbound cards default to collector number sort on initial load [ ] Add "Domain" option to sorting controls [ ] Domain sorting groups cards by their domain attribute [ ] User sort preference persists during session [ ] Sort options are clearly labeled and accessible [ ] Verify sort works correctly with all Riftbound cards

## Problem Statement Users cannot import an existing deck (already created in Flexslot) into a new Sideboard Guide. Currently, the only options are to import from text or create the deck from scratch, which is time-consuming and redundant when the deck already exists in the system. ## User Story As a Flexslot user who has already created decks in the platform, I want to be able to select one of my existing decks when creating a Sideboard Guide, so that I don't have to re-enter my deck list manually. ## Current Workflow (Problematic) User has an existing deck in Flexslot User wants to create a Sideboard Guide for that deck User must either: - Import the deck again via text (copy/paste from somewhere) - Manually recreate the entire deck from scratch This duplicates effort and creates potential for inconsistencies ## Expected Workflow User starts creating a new Sideboard Guide User sees option to "Import from My Decks" or similar User selects from a list of their existing decks Deck is automatically populated into the Sideboard Guide User proceeds to add sideboard notes and matchup information ## Area Sideboard Guides - Creation/Import flow ## Acceptance Criteria [ ] Add "Import from My Decks" option in Sideboard Guide creation [ ] Display user's existing decks in a searchable/filterable list [ ] Allow selection of a deck to populate the guide [ ] Properly link or copy deck data into the Sideboard Guide [ ] Handle edge cases (empty deck list, deleted decks, etc.) [ ] Consider whether to link to deck (synced updates) or copy (independent) [ ] Update UI to make the import option discoverable ## Questions for Stakeholder Should the Sideboard Guide link to the original deck (changes sync) or copy it (independent)? Should users be able to import decks from other users (public decks)? What happens if the original deck is deleted after being imported? ## Reporter CaptainJack (user feedback)

## Problem Statement The Collection Tracker has sorting issues where: Sorting sometimes works in the wrong direction (ascending vs descending confusion) The current sort state is not clearly communicated to the user ## Area Collection Tracker ## Current Behavior Clicking sort options sometimes sorts in unexpected direction Users cannot easily tell which column is being sorted Users cannot easily tell if sort is ascending or descending Sort behavior may be inconsistent across different columns ## Expected Behavior Clear visual indicator showing which column is currently sorted Clear visual indicator showing sort direction (arrow up/down icons) Consistent toggle behavior: click once for ascending, click again for descending Sort direction should match user expectations (A-Z, lowest-highest, etc.) ## Steps to Reproduce Navigate to Collection Tracker Click on a column header to sort Observe that sort direction may not match expectations Note lack of clear visual feedback on current sort state ## Technical Investigation Needed Audit all sortable columns in Collection Tracker Verify sort direction logic for each data type (text, numbers, dates) Check for state management issues with sort direction Review sort indicator UI components ## Acceptance Criteria [ ] All sortable columns have visible sort indicators [ ] Sort direction (asc/desc) is clearly shown with arrow icons [ ] Clicking a sorted column toggles the direction [ ] Clicking a new column sorts ascending by default [ ] Text columns sort A-Z (asc) and Z-A (desc) [ ] Numeric columns sort lowest-highest (asc) and highest-lowest (desc) [ ] Date columns sort oldest-newest (asc) and newest-oldest (desc) [ ] Sort state persists appropriately during session [ ] Add visual hover state to indicate columns are sortable ## Reporter CaptainJack (user feedback)

## Problem Statement The Collection Tracker is missing several features that users expect from a collection management tool: No export functionality No sharing capability No pricing/value information ## Area Collection Tracker ## Missing Features Detail ### 1. Export Functionality User Need: Ability to export collection data for backup, import into other tools, or personal records. Suggested Export Formats: CSV (spreadsheet compatible) JSON (developer/backup friendly) Plain text list PDF report (formatted summary) ### 2. Share Functionality User Need: Ability to share collection with others for trading, showing off, or collaboration. Suggested Share Options: Public link to view-only collection Private link with access code Social media sharing Direct share to other Flexslot users ### 3. Pricing Information User Need: See the monetary value of cards and total collection value. Suggested Pricing Features: Individual card prices (market/TCGPlayer/etc.) Total collection value Price trend indicators Value by set/rarity breakdown Price data source selection ## User Stories As a collector, I want to export my collection so I can back it up or use it in other tools As a collector, I want to share my collection so others can see what I have for trading As a collector, I want to see pricing information so I know the value of my collection ## Acceptance Criteria ### Export [ ] Add export button to Collection Tracker UI [ ] Support CSV export with all card data [ ] Support JSON export for data portability [ ] Include export options (all cards, filtered view, specific sets) ### Share [ ] Add share button to Collection Tracker UI [ ] Generate shareable public link [ ] Create view-only mode for shared collections [ ] Allow user to revoke/regenerate share links ### Pricing [ ] Integrate with pricing API (TCGPlayer, Scryfall, etc.) [ ] Display price per card in collection view [ ] Show total collection value summary [ ] Add price column to collection table [ ] Consider caching strategy for price data ## Questions for Stakeholder Which pricing source should be prioritized (TCGPlayer, CardKingdom, etc.)? Should prices be real-time or cached (with refresh option)? For sharing, should there be privacy controls (hide certain cards)? Should export include pricing data? ## Complexity Note This ticket contains 3 distinct features. Consider breaking into separate tickets: Collection Tracker: Export functionality Collection Tracker: Share functionality Collection Tracker: Pricing integration ## Reporter CaptainJack (user feedback)

## Problem Statement Users encounter a "Failed to add to collection" error when attempting to add a deck to a collection. This issue may be specifically related to creating a new collection during the add-deck-to-collection flow. ## Steps to Reproduce Open an existing deck Attempt to add the deck to a collection During the flow, create a new collection (rather than selecting an existing one) Observe the "Failed to add to collection" error ## Expected Behavior User should be able to add a deck to an existing collection successfully User should be able to create a new collection and add the deck to it in a single flow Success confirmation should be displayed after adding ## Actual Behavior Error message "Failed to add to collection" is displayed Deck is not added to the collection ## Acceptance Criteria [ ] Adding a deck to an existing collection works without errors [ ] Creating a new collection during the add-to-collection flow works correctly [ ] Deck appears in the target collection after successful addition [ ] Appropriate success/error feedback is displayed to the user [ ] Edge case: Handle scenario where collection name already exists ## Questions to Clarify Does this error occur when adding to existing collections, or only when creating new ones? Are there any specific error messages in the browser console or network requests? Does this affect all deck types or specific ones? --- Area: Collection Game: CaptainJack Type: Bug