Bug Reports

[CaptainJack] Cannot import existing deck into Sideboard Guide
## 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.) [ ] Create a full copy, dont just link an existing deck to a new sideboard guide [ ] Update UI to make the import option discoverable ## Questions for Stakeholder Should users be able to import decks from other users (public decks)? Answer: only from the deck detail page if they have access to the deck -- using a button or dropdown menu item like "Create new SB with this deck" What happens if the original deck is deleted after being imported? answer: nothing, this process is completely decoupled from the original deck. ## Reporter CaptainJack (user feedback)
0
[CaptainJack] Collection Tracker sorting issues - wrong direction or unclear
## 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)
0
[CaptainJack] Collection Tracker missing export, share, and pricing features
## 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)
1
·
under review
[CaptainJack] "Failed to add to collection" when adding deck to collection
## 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
4
·
under review
[CaptainJack] Battlefields, Chosen Champion, and Legend cannot be selected as foil
## Problem Statement Certain card types in CaptainJack - specifically Battlefields, Chosen Champion, and Legend - cannot be marked as foil in the deck builder or collection management interfaces. This prevents users from accurately tracking their foil versions of these card types. ## Steps to Reproduce Navigate to the Deck Builder or Collection for CaptainJack Find a card of type: Battlefield, Chosen Champion, or Legend Attempt to toggle the foil option for the card Observe that the foil toggle is either missing or non-functional ## Expected Behavior All card types should have the ability to be marked as foil (if foil versions exist) Foil toggle should appear and function the same as for other card types ## Actual Behavior Foil option is unavailable for Battlefield, Chosen Champion, and Legend card types Users cannot track foil versions of these cards ## Technical Notes This may be related to ticket #692d0380781355c8b374e56f (collection tracking issue for same card types). Both issues likely stem from the same root cause - these card types may not be properly recognized or configured in the system. ## Acceptance Criteria [ ] Battlefield cards can be toggled as foil [ ] Chosen Champion cards can be toggled as foil [ ] Legend cards can be toggled as foil [ ] Foil state persists correctly when saving deck/collection [ ] Foil versions display appropriate visual indicator ## Questions to Clarify Do foil versions of these card types actually exist in CaptainJack? Is this a data issue (cards missing foil metadata) or a UI issue (toggle not rendering)? --- Area: Deck Builder / Collection Game: CaptainJack Type: Bug Related: #692d0380781355c8b374e56f
0
[CaptainJack] Battlefields, Chosen Champion, and Legend not counted in collection tracking
## Problem Statement Collection tracking in the deck builder does not count cards of type Battlefield, Chosen Champion, and Legend. This means users cannot see ownership status for these card types when building decks, breaking the collection tracking feature for a subset of cards. ## Steps to Reproduce Add Battlefield, Chosen Champion, or Legend cards to your collection Navigate to the Deck Builder for CaptainJack Create or edit a deck containing these card types Observe the collection tracking indicators for these cards ## Expected Behavior All card types should show collection ownership status (owned/not owned counts) Deck builder should indicate how many copies the user owns vs. needs Collection tracking should work consistently across all card types ## Actual Behavior Battlefield, Chosen Champion, and Legend cards do not show collection tracking These cards appear as if user owns 0 copies regardless of actual collection Users cannot determine if they need to acquire these cards ## Technical Notes This is likely related to ticket #692d038142ef1ad26204ed00 (foil selection issue for same card types). Both issues suggest these card types may be misconfigured or missing from certain database queries/filters. Investigate: Card type enumeration/filtering logic Collection tracking query to ensure these types are included Data model for these card types ## Acceptance Criteria [ ] Battlefield cards show accurate collection count in deck builder [ ] Chosen Champion cards show accurate collection count in deck builder [ ] Legend cards show accurate collection count in deck builder [ ] Collection tracking totals include these card types [ ] "Cards needed" calculations account for these card types ## Questions to Clarify Are these card types stored differently in the database? Is there a card type filter that may be excluding them? --- Area: Deck Builder / Collection Game: CaptainJack Type: Bug Related: #692d038142ef1ad26204ed00
0
[CaptainJack] Cards hard to read when overlapping, menu covers card might
## Problem Statement Two related card readability issues in the deck builder: Overlapping Cards: When cards are displayed in a stacked/overlapping layout, they become difficult to read with no easy way to see full card details Menu Obstruction: The card action menu (triple dots/plus/minus buttons) covers the "might" value on cards, obscuring important game information ## Issue 1: Overlapping Card Readability ### Current Behavior Cards overlap each other in the deck view No hover-to-zoom or click-to-expand functionality Card text and details are cut off or unreadable ### Expected Behavior Users should be able to easily view full card details Hover/click should reveal complete card information Consider: zoom on hover, modal on click, or tooltip preview ## Issue 2: Menu Covers Card Might ### Current Behavior The action menu (three dots, +, - buttons) is positioned over the card's might value Users cannot see the might stat without dismissing or moving the menu ### Expected Behavior Card stats should remain visible when menu is displayed Menu should be repositioned to avoid covering critical card information Alternative: make menu appear on hover only, or position it outside the card ## Acceptance Criteria [ ] Users can view full card details through hover, click, or other interaction [ ] Card might value is not obscured by action menu [ ] Card text remains readable in all view modes [ ] Solution works on both desktop and mobile/touch [ ] Performance is not impacted by hover interactions ## Proposed Solutions ### For Overlapping Cards: Hover to raise card above others (z-index change) Click to open card detail modal/lightbox Tooltip with larger card preview on hover Adjustable card overlap/spacing settings ### For Menu Obstruction: Reposition menu to top-left or bottom of card Show menu on hover only (hidden by default) Use a floating action button outside the card area Make menu semi-transparent until hovered --- Area: Deck Builder / UX Game: CaptainJack Type: Bug / UX Improvement
0
Load More