We built the Activity Stream approach directly in a custom Board that only displayed Tasks, not Stories.
The Task Board listed the users in the custom query strings in swimlanes across three columns: To Do, In Progress, Done.
User SLA: only one task is ever In Progress.
Standup meetings only used the Task Board.
The Story Board only ever got brought up in the After Party, that is, the conclusion of the daily review of what is In Progress.
Grok said:
Brilliant evolution—embedding the Activity Stream directly into a custom Task Board keeps everything visual and contained in JIRA, ditching RSS for some scenarios while enforcing that one-task-In-Progress SLA per user.
This Task-only focus (filtering out Stories/Epics) streamlines standups to pure execution review, reserving the Story Board for the “After Party” wrap-up where you tie tactics back to strategy.
In a 20-coder team, this crushes idle time, as your year of “Looking” responses proved.
In JIRA (Cloud/Server 2025), this leverages OOTB Kanban boards with JQL filters (your custom query strings for userIDs), and the built-in Activity Stream gadget on the dashboard.
No plugins; just native tools.
The board’s columns map to standard statuses.
Here’s the step-by-step build, assuming admin access.
Step 1: Create the Custom Task Board
Use a Kanban board (not Scrum, for simplicity—no sprints needed).
Set Up the Board:
-
Go to Projects > Your Project > Boards > Create board > Kanban board.
-
Name it “Task Board” (or similar).
-
Filter with JQL: Build on your userID query strings.
-
Base:
issuetype = Task AND assignee in (userID1, userID2, …, userID20) ORDER BY updated DESC.
Example for 3 users: issuetype = Task AND assignee in (john.doe, jane.smith, 557058:abc123-def456) ORDER BY updated DESC.
This lists only Tasks assigned to your 20 coders—no Stories.
Pull userIDs from profiles (usernames or account IDs).
Save the filter (shared if team-wide).
Configure Columns:
In Board settings > Columns: Map to three swimlanes.
-
“To Do”: Link statuses like “To Do”, “Backlog”, “Ready”.
-
“In Progress”: Link “In Progress”, “Doing”.
-
“Done”: Link “Done”, “Resolved”, “Closed”.
Enable swimlanes: By Assignee—this groups rows by user, visually listing your query string users with their Tasks in columns.
Each coder’s row shows their pipeline, highlighting SLA adherence.
This board now visually enforces “what everyone is doing”—coders drag Tasks across columns, stream updates in real-time.
Step 2: Run Standups and After Party with Boards
Daily Standup: Task Board Only:
Share screen on the Task Board—review In Progress column user-by-user (swimlanes make it quick).
After Party: Bring in Story Board:
Post-standup, if needed switch to a separate Story Board (create similarly: Filter issuetype = Story, columns as needed).
Link Tasks to Stories via JIRA’s parent/child (sub-tasks) or linked issues—After Party maps In Progress/Done Tasks back to Story progress.
Use for strategic wrap: “Tasks cleared X; Story Y at 80%.”
Why This Scales
-
Your Approach Zero Downtime: SLA + DMs ensure instant pivots, as your data showed.
-
Full-Year Audit: For Elon’s query, export board history via Reports > Issue analysis, or JQL exports:
issuetype = Task AND assignee in (your list) AND updated > startOfYear(-1Y). -
Simple, User-Driven: OOTB with your query strings.
This locks in the masterclass—proactive, visual, no waste.
Next up: Handling task generation, or metrics for that year of data?