The banner plugin shows announcements where people actually see them: one global banner for the whole workspace (maintenance windows, policy notices) and one per-project banner managed by each project's own team (release freezes, sprint notices).
Where each banner is managed
- Global banner: Administration → Banner (workspace administrators only). Shows on every page, at the top. It can also show on the login page — useful for pre-signin maintenance notices (setting, on by default).
- Project banner: Project settings → Banner tab. Requires the
manage_bannerpermission and the Banner module enabled for that project (Project settings → Modules). Renders below the project's menu tabs, above the page heading.
Both can be active at once — the global bar at the top of the page, the project bar inside the project content area.
Per-banner options (both levels)
| Option | Details |
|---|---|
| Style | Info (blue) · Warning (amber) · Critical (red) · Maintenance (gray). Critical banners are announced to screen readers as alerts. |
| Text | Rendered with your workspace's text formatting (Markdown/Textile) — links, bold, and lists work; images and macros are stripped. |
| Schedule | Optional start and end datetimes (workspace timezone). Outside the window the banner hides automatically; future banners show a "scheduled" badge in settings, expired ones stay saved for reuse. |
| Dismissible | On by default — users close the banner with an ×, per user. If you edit the banner's text, style, or schedule, it automatically reappears for everyone who dismissed the old version. Turn dismissal off for critical maintenance notices that must stay visible. |
| Display scope (project banners) | Overview page only (default) · Overview + issue pages · All project pages. |
Suggested conventions
- Reserve Critical (non-dismissible) for genuine action-required notices — its impact fades fast if it's used for routine announcements.
- Use the schedule fields rather than manual on/off for maintenance windows: the banner retires itself on time, even if nobody remembers to.
- Project teams owning their own banners scales better than funneling every
notice through workspace admins — grant
manage_bannerto project manager roles and let the global banner stay rare.