...
Version 3.3 Release notes
22 March 2022
Info |
---|
For information on upgrading & downgrading, see Upgrading to version 3.3 |
Rw ui steps macro | ||||||
---|---|---|---|---|---|---|
Customizing My RequestsSome of our most requested features and improvements have been related to the My Request page and My Request module. We’ve packed this feature full of new additions and improvements to make it even better. You’ll now have full control and more flexibility when displaying customer requests. All end users that have an account and access to the My Request page will now benefit additionally from the following: Improved filtersIn addition to the previously existing filters, we’ve added filters based on Location. This includes filtering on portals or any Refined item in the navigation structure such as a Category or a Site. We’ve also added a search bar within the module so that you can quickly get back to that one ticket regarding the foosball table you requested. Column manipulation: Add, remove, sort, & rearrangeYou’ll now be able to add and remove columns to the My Requests page. If the field supports it, you’ll also be able to sort on the column in ascending/descending order. Finally it’s also possible to rearrange the columns in whatever order suits best. Updated designThe view has gotten an updated design and will now not only look better, but work better as well on different screen sizes.
More options for the My Request ModuleOf course the My Request module has also reaped the benefits of the new improvements. It’s now possible to further configure the module with predefined filters, columns and display options. There’s also the ability to further filter with additional queries (JQL) to allow for any conceivable use-case.
Languages & Dictionary improvementsContinuing on the 3.2 release features, we’ve further improved Languages as well as the Custom text variable & Dictionary feature. You can now add your own languages to the language switcher. The Custom text variables now benefit from: Import / Export text variablesExport custom text variables as Additional filteringQuickly search and find the key you’re looking to edit, filter to only show empty or translated values or just values for a certain language. TagsYou can now tag variables. This can be helpful to group related variables, for example per site or landing page, or to create tags for the type of message/variable.
Request Type ModuleThe request type module has gotten an overhaul with an updated design and new display options for the request type groups:
For the request types themselves there’s also new layouts available:
In addition to this you can also choose which request types to display; either individually or per group, from the current portal or from any other. This means you can now display request types and launch create dialogs from other portals without losing the context of the current one.
Refined AdminsFrom the Jira Administration pages, you’ll now have direct links to all Refined Sites from the Refined dropdown. For many of the administrator features, selecting locations is now much easier with searchable selectors for things like:
Additional features & improvementsAs usual, we have also included multiple bug fixes and improvements into this release. 93 customer requests resolved in this release. Some additional highlights include:
|
...
Version 3.3 Upgrading instructions
Info |
---|
We always recommend to first always upgrade on a separate test/staging instance first, to see if everything works as expected. |
Before upgrading, make sure that you have Jira version 8.6.0 or higher/Jira Service Management version 4.6.0 or higher.
Install version 3.3 via the UPM, or download and install it via the Atlassian marketplace.
...
The drawback here is that any changes made to My Requests module, Request Types module modules or the global My Requests overview pages while on the 3.3 version will not be transferred back to 3.2. Similarly, the automatic upgrade that prepares these modules only runs once, so any new changes made to the module once back on 3.2 will not migrate over once a new 3.3 upgrade is made. In that case, we recommend simply configuring up these modules again. You can export and store the old version of the layout and use that as the basis for updating.
...