Release notes

Bug fixes and minor improvements implemented within the app.

Two steps required after updating

Reorder instances and tabs

You can now set the order of the instance tabs and of the request tabs in each instance. Select Reorder next to the Instance field on Configure tabs, and drag the items or use the arrows. The order of instances is saved for each dialog variant. Until you set an order, nothing changes. No action needed. See Request Tabs.

Instance tab names in Configure tabs

You now set the name of an instance tab in Configure tabs, in the Instance tab name field, instead of on the Connections screen. Each dialog variant can use a different name. UniPortal moves your existing names, so no action is needed. See Request Tabs.

Show the customer’s name in HTML blocks

You can now add the placeholder {{user.displayName}} to HTML (top) and HTML (bottom) to greet customers by name, for example “Welcome, Jan Kowalski!”. Add a fallback with {{user.displayName|there}}. No action needed. See HTML Block.

Hide the Go to Help Center tile

You can now hide the Go to Help Center tile for each tab with Show Go to Help Center tile. The tile stays visible until you turn it off. No action needed. See Request Tabs.

Remove logos and icons, and a clearer layout editor

You can now remove an uploaded logo, external link icon, or JQL counter icon without deleting the link or counter. The Configure tabs screen has a new layout, and Add link and Add JQL add an empty item. No action needed. See Logo & Header, External Links, and Request Tabs.

Select Open and Closed requests together

Customers can now select Open requests and Closed requests together in the status filter of the dialog. No action needed. See View on Customer Portal.

This release also includes bug fixes for the request table, the Salesforce and Azure DevOps tabs, and the requests of portal-only customers on connected instances. Customers no longer see the Allow access message that only a site admin can act on.

Dialog variants

You can now show a different dialog to each Jira group or JSM organization. Every variant has its own General settings and its own tabs, so employees and managers can see different banners, links, and tabs. No action needed. See Dialog Variants.

Request tabs

You can now add up to 10 request tabs per instance for Jira Service Management, Salesforce, and Azure DevOps. Each tab has its own title, columns, and filters, and JSM tabs can also have a Tab JQL and their own JQL counters. This lets you split one instance into separate views, such as incidents and service requests. No action needed. See Request Tabs.

Configuration on a single instance

You can now configure the dialog and its tabs on a single instance right after you install UniPortal, without authorizing that instance first. This makes the first setup shorter. No action needed. See Installation.

Handling of a disabled REST API

UniPortal now detects when the REST API is disabled on a connected JSM instance. It shows a banner on the Connections and Edit layout screens and makes both read-only until the instance answers again. This makes it clear why you can’t change the configuration, instead of showing an unrelated error. If you see the banner, check the REST API setting of the instance named in it. See the FAQ and Connections.

Set as master

You can now make any connected instance the master with Set as master in the Connections table. The master is the only instance where you edit the layout, so you can move it to the instance where your team works. No action needed. See Connections.

UniPortal 1.0.0 is the first release. It turns one or more Jira Service Management instances, plus Salesforce and Azure DevOps, into a single customer-facing dialog that you design and configure yourself. To start, install UniPortal and follow Installation. For an overview, see Welcome to UniPortal.

Connect several JSM instances

The Connections screen lists the current instance and every connected instance. You can rename a connection, edit the layout of a single instance, remove a connection, and refresh the list. This gives you one place to manage all your instances. See Connections.

Salesforce and Azure DevOps

You can connect Salesforce to show its objects and records, and Azure DevOps to show work items from its projects, each in its own tab in the dialog. See Salesforce and Azure DevOps.

Design the dialog

In General settings you can upload a logo, set a header, add HTML blocks above and below the external links, and add external links. A dialog asks what to do with unsaved changes when you leave the screen. This lets you brand the dialog and post announcements directly in it. See Create Layout.

Request table for each instance

For each instance you configure which columns the request table shows, and up to three JQL counters that you can edit and restore to their defaults. Customers see a table per instance, a search by summary, a status filter, and the counters. This lets each service desk show the requests that matter to it. See Request Tabs.

Custom columns

The request table supports SLA, user picker, Assets, and group picker fields as columns. See Request Tabs.

Dialog on the customer portal

The dialog opens automatically when a customer follows the right link on the portal. It shows the logo, header, HTML blocks, and external links. A customer sees an external link only if they have access to the portal it points to. See View on Customer Portal.