resolved
Jira
atlassian.com/jira/software/projects/{key}/boards/{id}
landed in 38msBookSlash for Jira · Engineering
b/sprint, b/backlog,
b/bugs.
Jira URLs are infamous: long, mostly-numeric, and identical across half the queries you actually use. With BookSlash, the engineering team’s active sprint, the open-bug queue, and the parking-lot backlog each live behind a name everyone remembers.
sprint
other shortcuts you might save
b/sprintb/backlogb/bugsb/burndown
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Jira, with notes on why each one survives the URL changes that break personal bookmarks.
- b/sprint
The currently active sprint board.
Every standup opens with this URL. Saving it as a slug ends the daily "anyone got the link?" ping.
https://{workspace}.atlassian.net/jira/software/projects/{key}/boards/{id} - b/backlog
Refined backlog ready for upcoming sprint planning.
Product managers, engineering leads, and stakeholders all need it.
https://{workspace}.atlassian.net/jira/software/projects/{key}/backlog - b/bugs
Open-bug filter, sorted by severity.
On-call rotation reaches it daily; QA reaches it every sprint review.
https://{workspace}.atlassian.net/issues/?jql=type%3DBug+AND+resolution%3DUnresolved - b/burndown
Sprint burndown chart for the current iteration.
Eng manager and team lead check it daily; saved filters break across versions of Jira but the slug doesn’t.
https://{workspace}.atlassian.net/jira/software/projects/{key}/reports/burndown - b/epics
Active epics across the team.
Roadmap reviews and exec updates always reference this view.
https://{workspace}.atlassian.net/jira/software/projects/{key}/boards?epic=true - b/resolved
Resolved tickets awaiting QA verification.
QA opens this every morning; saving it as a slug is faster than navigating Jira’s sidebar.
https://{workspace}.atlassian.net/issues/?jql=resolution%3DDone - b/jql-<query>
Pattern for shared JQL queries (b/jql-flaky-tests, b/jql-stale-prs).
JQL strings rot — by saving them as slugs you can rewrite the query without retraining the team.
https://{workspace}.atlassian.net/issues/?jql={query}
Common workflows
Three patterns that pay back in week one.
01
Standup, every morning, in one keystroke
The standup channel’s pinned URL inevitably drifts when someone clones a sprint. Saving the sprint URL as b/sprint means the team types one shortcut, lands on the live sprint, and the eng lead can re-target the slug whenever the sprint number rolls forward.
02
Bug-triage shortcut for QA + on-call
b/bugs points at a JQL query like priority in (Highest, High) and status = Open. QA leads update the filter quarterly; the slug stays. On-call pages now include the slug in the runbook so engineers go from page → b/bugs → triage in three keystrokes.
03
Roadmap reviews without "send me the link"
Engineering leadership reviews b/epics every other week. Same slug, same audience, same destination — even when the underlying Jira filter is rebuilt to add a new project key.
With and without
Same Jira. Different team experience.
Without shortcuts
A Slack channel pinned with five Jira URLs from six months ago. Half of them 404 after a project rename. Every standup starts with someone re-pinning the sprint board.
With BookSlash
b/sprint, b/backlog, b/bugs. Pin the slugs once; the destinations stay current as Jira evolves. New engineers learn three shortcuts and never ask for the standup link again.
Related integrations
Pair Jira with one of these.
Frequently asked
BookSlash + Jira
Only if you point it at a sprint-number-specific URL. Most teams point b/sprint at the board view (Sprints → Active sprint), which Jira keeps current automatically as sprints roll. For sprint-specific archives, use a dated pattern like b/sprint-q4-2026.
Both. Slugs are URL → URL redirects; the destination is just a string. Jira Data Center URLs work identically (your team still needs network access to the destination).
Yes — use namespaced slugs like b/eng-sprint, b/design-sprint, b/sales-sprint. Each team owns a slug, no naming collisions, the b/ pattern stays consistent.
One edit in BookSlash → Settings → Slugs, or a single curl call to the API. Every teammate keeps typing b/sprint; the destination flips silently. The audit log records who changed the URL and when.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial