Card & Story
The Card & Story screen is a project's agile view: this is where you create and track work items (cards and stories), organize them by epic and, for Scrum projects, by sprint. You reach it from the Card & Story menu in the project sidebar.
- Kanban / Scrum — the screen offers the full agile experience: Backlog board, epics, swimlanes, sprints.
- Gantt (planned) — the screen is still available, mainly in Table view, to manage cards linked to tasks.
The two views: Backlog and Table
At the top of the screen, a View switch lets you toggle between:
- Backlog — the Kanban board: cards are spread across columns (statuses) and moved by drag and drop.
- Table — a tabular list of cards, handy for filtering, sorting and bulk editing.
Card types
A card can be of several types:
| Type | Use |
|---|---|
| 📘 Story | A functional item to deliver (user need) |
| 🐞 Bug | A defect to fix |
| ⚙️ Action | An attached subtask / concrete action |
A card can be linked to a parent task in the planning. In that case it inherits by default the same period as the parent task, and stays of type Story unless changed.
Organizing with epics
On Kanban and Scrum projects, an Epics panel is shown on the left:
- Add an epic via the ＋ icon
- Collapse / expand each epic to see its statistics (number of cards per status)
- All tickets — shows every card in the project
- Tickets without epic — isolates cards not attached to any epic
Epics group cards into broad themes; they sit one level above stories.
Sprints (Scrum projects)
For a Scrum project, a Sprint button lets you create a sprint. Cards are then planned into iterations. If there is no active sprint, FoxPlan states it explicitly.
Creating and editing a card
- Add Card / Add Story creates a new item
- When creating / editing, you fill in:
- Card name (required)
- Type (Story, Bug, Action)
- Kanban column / status (required)
- Assignee (required for a linked card)
- Description
- Bulk import (⏬ Bulk import of card icon) lets you create multiple cards at once.
Tickets created by resources (private / public)
By default, only people with an editing role on the project (Project Admin, Project Lead) can create cards. You can however allow the project's resources to create their own tickets.
Enabling the option
In Definition & members → Card & Agility tab, tick "Allow resources to create their own tickets".
Once the option is on, every project resource sees the ＋ button at the top of the columns and can create their own cards — even if the rest of the project stays read-only for them.
An authorized resource can only create, edit and delete their own cards (the ones they created / own). They cannot modify other people's cards.
Private or public card
When created, a card has a visibility:
| Visibility | Icon | Who sees it |
|---|---|---|
| Private | 🔒 lock | The creator only — invisible to everyone else, including project administrators |
| Public | — | All project members |
- A card created by a resource is private by default.
- The Private / Public toggle is in the card's edit panel (header, next to the status).
- Private cards are flagged with a lock on the board.
A private card is never visible to another user, whatever their role (neither project lead nor administrator). To share a card with the team, switch it to Public.
Who can make a card private?
The Private / Public lock only appears in the edit panel when all of these conditions are met:
- the project has the "Allow resources to create their own tickets" option enabled;
- the card is assigned to you — you are its owner (person in charge);
- you are its creator.
In every other case the lock is hidden (visibility cannot be changed). In particular:
- a card with no owner cannot be made private;
- only the card's owner (and creator) can toggle it private / public;
- on a project without the option, the lock appears for nobody.
Search and filter
The toolbar offers several sorting aids:
- Search by card and parent task
- Time filters: +0 (today), +7 (this week), +30 (this month)
- Cards to be started and Cards to be closed (alert icons) to spot delays
- Filter by assignee: click a resource's avatar to see only their cards
- Favorites: save a combination of filters to reuse it
Kanban layout
On Kanban / Scrum, two layouts are available via the toggles in the top right:
- Flat — all cards within the status columns
- By resource — board grouped by owner (swimlanes)
See also
- Project management — project creation and planning
- Project members — who can edit cards depending on their role
Use the +0 / +7 / +30 filters daily to stay focused on the cards to handle in the short term, and save your recurring filters as a favorite.