Jira Announcement Banner FAQ: Customization, Scheduling & Best Practices
Announcement banners are one of the few communication channels in Jira that guarantee visibility. Unlike emails that get buried in crowded inboxes or Slack messages that scroll past in minutes, a banner sits at the top of every Jira page until an administrator removes it. That makes banners the right tool for maintenance notifications, policy changes, security alerts, and any information that every Jira user -- or a specific subset of users -- needs to see.
But Jira's built-in announcement banner has significant limitations. It supports only plain text. There is no way to schedule it. It is visible to every user on the instance with no option to target specific teams or projects. Only one banner can be active at a time. And enabling or disabling it is a manual process that someone has to remember to do, which means banners often stay live long after the information they contain becomes irrelevant.
Modern Announcement Banner for Jira extends Jira's native banner system with the features teams actually need: a saved announcement library for quick reuse, dismissible banner options, public/private visibility control, and one-click switching between saved announcements. This FAQ answers the most common questions about Jira announcement banner customization and explains how Modern Announcement Banner helps manage the gaps in the native experience.
Does Jira have a built-in announcement banner?
Yes. Jira Cloud includes a native announcement banner that administrators can enable through the system settings. It displays a single line of plain text at the top of every Jira page, visible to all users on the instance. The configuration is minimal: you type your message, toggle the banner on, and it appears. Toggle it off, and it disappears.
For simple use cases -- a single sentence reminding everyone about an upcoming holiday, for example -- the native banner works. But the limitations become apparent quickly when you need to do anything beyond plain text. You cannot add links, so if you want to direct users to a Confluence page or an external resource, you have to include a raw URL and hope people copy and paste it. You cannot format the text with bold, italic, or color, which means important details cannot be visually distinguished from the rest of the message. You cannot include bullet lists, so multi-item announcements must be crammed into a single paragraph.
More fundamentally, the native banner is all-or-nothing. It is visible to every user on the instance. There is no way to restrict it to a specific project, team, or group. If the engineering team needs to see a maintenance notice but the sales team does not, the native banner cannot make that distinction. And only one banner can be active at a time, so if you have two different announcements that need to run concurrently -- a maintenance window and a new policy rollout, for instance -- you have to combine them into a single message or choose one over the other.
Modern Announcement Banner for Jira addresses several of these gaps. It provides a saved announcement library so you can prepare banners in advance and activate them with one click. It supports dismissible banners that users can close after reading, and persistent banners that remain visible until an admin disables them. It offers Public and Private visibility settings. It is important to note that the app uses plain text only (no rich text formatting or clickable links), does not support automatic scheduling, and allows only one active banner at a time -- but it makes managing and reusing announcements significantly easier than the native Jira banner.
Can I schedule announcement banners in Jira?
Neither Jira's native announcement banner nor Modern Announcement Banner currently supports automatic scheduling. An administrator must manually enable the banner when they want it to appear and manually disable it when it is no longer needed. This creates two common failure modes. The first is forgetting to enable the banner on time, which means the announcement goes unseen during the critical window. The second is forgetting to disable it, which means a stale banner about an event that already happened continues to clutter every Jira page for days or weeks until someone remembers to turn it off.
Both failure modes are common in practice. The person responsible for the banner is often the same person managing the maintenance window, the policy rollout, or the incident response -- all of which are high-pressure situations where toggling a Jira banner is easy to forget. And once the dust settles, going back to clean up the banner feels like a low priority compared to the work that just finished.
Modern Announcement Banner for Jira mitigates this by letting you pre-create and save announcements in advance. You can prepare a maintenance window banner ahead of time and enable it with one click when the window approaches, rather than composing the message under pressure. After the event, disable it just as quickly. While it does not auto-schedule, the saved announcement library reduces the friction of manual management significantly.
Can I show different banners to different teams in Jira?
Targeted communication is one of the most requested capabilities for Jira announcement banners, and it is something neither the native banner nor Modern Announcement Banner currently supports with granular control. When you enable a banner, every user on the instance sees it regardless of their role, group membership, or the projects they work on.
Modern Announcement Banner for Jira does offer a Public/Private visibility setting. Public banners are visible to all users, while Private banners follow Jira's privacy settings. However, granular group-based or project-based targeting -- such as showing a banner only to the engineering team or only within a specific project -- is not currently supported.
The best workaround for team-specific communication is to use the banner for company-wide announcements and rely on other channels (Slack, email, Confluence) for team-specific messages. When you do need a banner that is relevant to only some users, the dismissible option lets those who are not affected close it after reading, reducing the noise impact.
How do I add links and formatting to Jira banners?
Both Jira's native announcement banner and Modern Announcement Banner accept only plain text. No bold, no italic, no hyperlinks, no lists, no color. If you want to include a URL, it appears as raw text that users must copy and paste into their browser. If you want to emphasize a date or a deadline, you cannot make it bold or red. If you have three separate points to communicate, you must concatenate them into a single unbroken string.
This limitation is more than an aesthetic problem. Plain text banners are harder to scan, harder to act on, and more likely to be ignored. A banner with a clear structure -- headline, explanation, and a URL to detailed instructions -- communicates its message faster. But with plain text, you must rely on punctuation and careful wording to convey emphasis.
Modern Announcement Banner does support emojis in banner messages, which can help draw attention. Use emojis strategically -- for example, a warning triangle emoji before a maintenance notice, or a calendar emoji before a deadline. While not a replacement for rich formatting, emojis can make plain text banners more scannable.
For actionable banners, include the full URL as plain text and keep messages under 200 characters for best readability. Compose the URL to be as short and memorable as possible, or use a URL shortener if the target link is long.
Can I use announcement banners for maintenance windows?
Announcement banners are the ideal channel for maintenance window notifications in Jira because they appear in the tool where work is already happening. Unlike an email that competes with dozens of other messages or a Slack notification that disappears in the feed, a banner is persistently visible every time a user loads a Jira page. That continuous visibility is exactly what you want for a maintenance window: the information stays top of mind from the moment it becomes relevant until the window closes.
The recommended approach for maintenance window banners depends on the timeline. For maintenance scheduled a week or more in advance, create a dismissible banner with the date, time, duration, and impact. The dismissible option lets users acknowledge that they have seen the notice and removes the banner from their view for their current session, which prevents banner fatigue during the lead-up period. Include a plain-text URL to a Confluence page or status dashboard with full details.
As the maintenance window approaches, edit the banner to make it non-dismissible (uncheck the Dismissible setting). This ensures that even users who dismissed the advance notice see the final reminder.
After the maintenance window closes, disable the banner manually. Users who return to Jira after maintenance and see a banner about it may assume the maintenance is still in progress or that something went wrong. With Modern Announcement Banner, you can pre-save both the advance notice and the maintenance-in-progress banners, then switch between them with one click -- but you do need to remember to disable the banner when the window closes.
For recurring maintenance windows, save the banner as one of your stored announcements so you can re-enable it quickly each time the window comes around.
How do Modern Announcement Banner banners differ from Jira's native banner?
The differences between Modern Announcement Banner for Jira and Jira's native announcement banner fall into several categories, each of which addresses a specific limitation of the built-in option.
Text formatting. Both the native banner and Modern Announcement Banner support plain text only. Neither offers rich text, bold, italic, clickable links, or color. Modern Announcement Banner does support emojis in banner text.
Scheduling. Neither the native banner nor Modern Announcement Banner supports automatic scheduling. An administrator must manually enable and disable banners in both systems. Modern Announcement Banner mitigates this by letting you save announcements in advance and enable them with one click.
Targeting. Both the native banner and Modern Announcement Banner are visible to all users (or follow Jira's privacy settings in Private mode). Granular group-based or project-based targeting is not available in either system. Modern Announcement Banner offers Public and Private visibility settings.
Multiple banners. Both the native system and Modern Announcement Banner support only one active banner at a time. Enabling a new banner automatically disables the current one. However, Modern Announcement Banner lets you save multiple announcements and switch between them with one click, making it faster to change the active banner.
Dismissible options. The native banner is always visible until an administrator removes it. Modern Announcement Banner lets you configure banners as dismissible or persistent. Dismissible banners allow users to close them for their current session, which is appropriate for informational announcements. Persistent banners remain visible until disabled, which is appropriate for critical alerts.
Announcement management. The native banner is a single configuration field. Modern Announcement Banner provides a full management interface where you can save unlimited announcements for reuse, switch between them with one click, and maintain a library of messages for common scenarios.
Feature comparison: Native Jira Banner vs Modern Announcement Banner
The table below compares Jira's built-in announcement banner with Modern Announcement Banner across eight key capabilities.
| Feature | Jira Native Banner | Modern Announcement Banner for Jira |
|---|---|---|
| Text formatting | Plain text only. No bold, italic, color, or HTML. | Plain text with emoji support. No rich text, links, or HTML. |
| Scheduling | No scheduling. Administrator must manually enable and disable the banner. | No automatic scheduling. Manual enable/disable, but pre-saved announcements enable faster activation. |
| Audience targeting | Global visibility. Every user on the instance sees the banner. | Public or Private visibility. Granular group/project targeting not supported. |
| Multiple banners | Only one banner can be active at a time. | Only one banner can be active at a time. Multiple saved announcements can be switched between with one click. |
| Links and actions | Raw URLs only. Users must copy and paste links manually. | Raw URLs only. No clickable links (plain text). |
| Dismissible behavior | Always visible until administrator disables it. | Configurable per banner: dismissible (user can close for session) or persistent. |
| Banner management | Single configuration field with no history or reuse. | Full management interface with saved announcements, one-click switching, and unlimited saved messages. |
| Visibility control | No visibility options. | Public or Private toggle. |
Banner use cases
Understanding when and how to use announcement banners is just as important as knowing which tool to use. Below are five practical scenarios where announcement banners deliver clear value, along with specific recommendations for each.
Scheduled maintenance window
Maintenance windows are the most common and most time-sensitive use case for announcement banners. Jira administrators need to notify all users -- or a specific subset -- that the system will be unavailable during a defined period. The banner should appear well in advance, remain prominent as the window approaches, and disappear immediately after maintenance concludes.
Configure the banner with a bold headline ("Scheduled Maintenance"), the exact date and time window, expected duration, and a link to a status page or Confluence document with details. Use scheduling to automate the lifecycle: set the start date to one week before maintenance and the end date to the planned completion time. If the maintenance only affects certain projects, use project-based targeting to keep the banner invisible to unaffected teams.
New policy or process rollout
When a team or organization introduces a new process -- mandatory code reviews, updated time tracking requirements, new issue creation standards -- an announcement banner ensures the change does not go unnoticed. Unlike a one-time email that people read and forget, a banner provides continuous visibility during the transition period.
Write the banner with a brief summary of the policy change, the effective date in bold, and a clickable link to the full documentation. Make the banner dismissible so users can acknowledge it once they have read and understood the change. Set a two-to-four-week schedule so the banner naturally expires once the new process has been adopted. Use group targeting if the policy only applies to certain teams.
Incident response and emergency alerts
During an active production incident, speed of communication is critical. An announcement banner in Jira can alert all relevant teams that an incident is in progress, point them to the incident response channel, and provide a link to the real-time status dashboard.
For incident banners, use persistent visibility (non-dismissible) so the alert cannot be closed until the incident is resolved. Use bold red text for the incident status to create visual urgency. Include direct links to the Slack incident channel and the status page. Once the incident is resolved, update the banner to reflect the resolved status briefly before scheduling it to auto-remove an hour later.
Onboarding and welcome messages
New team members joining a Jira instance benefit from a welcome banner that points them to key resources: the team wiki, onboarding documentation, project conventions, and points of contact. This is a low-urgency but high-value use case that helps new users orient themselves during their first days.
Keep the tone friendly and informative. Use bullet lists to link to multiple resources. Make the banner dismissible since it only needs to be seen once. Target the banner to a "new-users" group if your organization provisions one, or keep it global with a two-week schedule for new hires. Save the banner as a reusable template so it can be quickly re-enabled each time a new cohort joins.
Compliance and audit notifications
Organizations subject to compliance requirements -- SOC 2, GDPR, HIPAA, or internal audit standards -- often need to communicate mandatory actions to specific teams. An announcement banner ensures the communication is visible within Jira where the relevant work is happening, rather than relying solely on email.
Craft the banner with precise language about the required action, the deadline in bold, and a link to the compliance documentation or form. Target the banner to the specific groups responsible for the action -- the security team, the data engineering team, or the finance team -- rather than broadcasting it to the entire organization. Set the end date to the compliance deadline. Use persistent visibility to ensure the banner cannot be dismissed until the required action is completed.
Related resources
- Modern Announcement Banner for Jira — full documentation, setup guide, and configuration reference
- Browse all NGPILOT apps — explore the complete suite of Jira and Confluence apps by NGPILOT