Getting started
Install
- In Jira, open Apps → Explore more apps and search for Portal Notices.
- Click Get app and follow the steps. Jira admins install apps for the whole site.
Your first notice (about 30 seconds)
- Open Settings (⚙) → Apps → Portal Notices.
- Pick a template — Planned maintenance, Outage, Resolved, Holiday hours, Longer replies, New request form — or start blank.
- Choose a design and a tone. The preview shows exactly what customers will see.
- Under When, leave the dates empty to start now, or set a start and end. Tick Repeat every week for regular hours.
- For planned work, tick This notice announces a time window and set when it starts and ends. See Maintenance windows.
- Under Where and who, leave everything empty for the help center and every portal, or narrow it down (see below).
- Click Publish. Customers see it on their next page view.
Where and who
- Everyone / Signed in / Not signed in: who sees it. "Not signed in" is for visitors of public portals.
- Portals: empty means the help center and every portal. Picking portals keeps the notice off the help center, which belongs to no portal.
- Pages: the help center, portal home, request form, request details, my requests, approvals and profile.
- Request types: only on the request form and requests of these types — for example a tip on the "Laptop problem" form.
- Customer organizations: only customers in these organizations, for notices meant for one client. Organizations only apply to signed-in customers.
Every list narrows the audience; a customer has to match all of them.
Writing the message
boldmakes text bold.link textadds a link. Jira asks before opening sites outside Jira.- Links can also point inside Jira, such as a request form:
Report it. These open in the same tab. - Line breaks are kept.
A button
Fill in Button label and Button link to add one button under the message. The link can be a web address (https://…, opens in a new tab) or a path inside Jira such as /servicedesk/customer/portal/1/create/5 (opens in place). Both fields are needed; links that aren't web addresses or Jira paths are refused. Notices without a button look as before.
Closing
- By default customers can close a notice with ✕. Choose After someone closes it, show it again to bring it back after a day, a week or 30 days.
- Tick Show each person once for notices that need no ✕: after a customer has seen the notice, it doesn't come back, even if you edit it. A repeating notice shows once per repeat. Visitors who aren't signed in are remembered by their own browser.
- Turn off Customers can close it for outages everyone must see. Those always stay, whatever else is set.
Your own templates
Click Save as template under any notice. It keeps the text, button, design, color, audience, repeat and closing settings — not the dates. Jira admins and each portal keep their own templates.
Project admins
Service project admins find the app in Project settings → Apps → Portal Notices and can post notices that show only on their portal. A Jira admin can turn this off in the app's settings.
Something not working?
Open 🩺 Check setup at the bottom of the app's sidebar. It tries storage, the subscription, portals, request types and customer organizations, and says in plain words what to fix.