IMPORTANT: If you use the custom js/css and footer feature, you should back this up before updating the app, otherwise you risk losing your scripts.
This release rolls back a feature where user could modularize custom js and css. The functionality gave unintended side effects, and has been moved back to be considered in a future release.
This release rolls back a feature where user could modularize custom js and css. The functionality gave unintended side effects, and has been moved back to be considered in a future release.
New Feature:
Modularize custom JS and CSS so clients can write it on organized code containers
Bugfixes:
Popup error 500 displayed when sending feedback
Test for Customizer with JSM 5.4.0 and java 11 is a bit unstable
"Search" Issues post upgrade
New Feature:
Modularize custom JS so clients can write it on organized code containers
Bugfixes:
Popup error 500 displayed when sending feedback
Test for Customizer with JSM 5.4.0 and java 11 is a bit unstable
"Search" Issues post upgrade
Fix: Column contents were sometimes displaced in request.
Feature: Layout for the vertical display of categories is now an option.
Aesthetics: Ultimate Customizer's new logo.
Updated dependencies to fix vulnerabilites in third-party frameworks
Updated dependencies
- Fixed csv export sometimes getting statuses wrong when exporting to .csv
- Re-enabled module based design on most pages including: signups, approvals, single portal, portals page, user login, profile, create request, view request, and requests page - Fixed permission error when editing login screen
- Fixed a bug with additional fields on request view
- Fixed csv export sometimes getting statuses wrong when exporting to .csv
- Re-enabled module based design on most pages including: signups, approvals, single portal, portals page, user login, profile, create request, view request, and requests page - Fixed permission error when editing login screen
- Fixed a bug with additional fields on request view
Fixed Chrome UI error
Fixed Chrome UI error
First release after acquiring the app in early January.
-Fixed stability issues, (error on the log-in page, infinity wheel on loading portals, validations on create request screen, layout positioning issues, and many more)
-Link to new documentation space
-Created the technical foundation to improve the app with new features
First release after acquiring the app in early January.
-Fixed stability issues, (error on the log-in page, infinity wheel on loading portals, validations on create request screen, layout positioning issues, and many more)
-Link to new documentation
-Created the technical foundation to improve the app with new features
Knowledge base pages (linked from search results on the portals page), can no longer be edited with module design. This is to prevent iframe rendering problems.
Knowledge base pages (linked from search results on the portals page), can no longer be edited with module design. This is to prevent iframe rendering problems.
Changed the way the bootstrapping of the plugin works
Changed the way the bootstrapping of the plugin works
Improved loading of UI elements (page load, and page change)
Improved loading of UI elements (page load, page change)
We added two majors features: Public portals: In permissions (menu), enable per-portal "anonymous" access. When creating a request, the user is forced to input a valid email (captcha protected). When the request is created, the user is instantly signed in, and a "set password" mail is sent.Request types visibilityGo to a portal (admin), and click Request types visibility. Now configure on a per-request type basis. You can limit visibility to groups and organisations, or disable a type completely.
We added two majors features:
Public portals: In permissions (menu), enable per-portal "anonymous" access. When creating a request, the user is forced to input a valid email (captcha protected). When the request is created, the user is instantly signed in, and a "set password" mail is sent.
Request types visibility: Go to a portal (admin), and click Request types visibility. Now configure on a per-request type basis. You can limit visibility to groups and organisations, or disable a type completely.
1. Added better design for the new Atlassian Service Desk design
2. Description now renders as HTML in details of an request (if added as an additional field)
3. Search fields did not properly align in new Service Desk theme
4. Satisfaction value is shown properly in request list
5. Column/field in request list only show if at least one request has a value for the field6. Fields set up in the 3.2.X versions did not show up in some cases
7. Xporter (plugin) buttons now show up in module based design as well
1. Added better design for the new Atlassian Service Desk design
2. Description now renders as HTML in details of an request (if added as an additional field)
3. Search fields did not properly align in new Service Desk theme
4. Satisfaction value is shown properly in request list
5. Column/field in request list only show if at least one request has a value for the field
6. Fields set up in the 3.2.X versions did not show up in some cases
7. Xporter (plugin) buttons now show up in module based design as well
in some cases, if an admin inputs wrong formatted js/css, the service desk pages fails to load.
With these urls:
..the content can be cleared
in some cases, if an admin inputs wrong formatted js/css, the service desk pages fails to load.
With these urls:
..the content can be cleared
Jira 8.0 / Service Desk 4.0 support!
The requests page does now have:
Note: you need to re-set up fields/search fields + override names.
Fixes:
Jira 8.0 / Service Desk 4.0 support!
The requests page does now have:
Note: you need to re-set up fields/search fields + override names.
Fixes:
The status selection on Requests does now only show Status values that belong to projects that the user can see
There is no need to update.
- some times status did not show up for localised profile users(myrequests)
- some requests type icon did not show up for localised profile users (myrequests)
Fixes for:
- fixed a bug where the plugin failed on Oracle DB
- user chosen fields are now saved in DB (and used in CSV export)
- status name is translated to user lang
- the Service Desk status is now shown (if set) instead of real status for the status field
Added Customer Request Type as a additional field. This will show the name (not icon, which already is in the list)
In the options for Requests module, the admin can choose that the user can select which fields the user want to see (like just Priority out of fields Priority, Resolution and e.g. other fields chosen by admin).
Requests page now shows 20 instead of 10 requests.
Added due date + custom field types Date/Datetimepicker to "Requests"
Bug fix: Some SQL queries for database did not work on MSSQL and Oracle.
New feature: Add SLA's to My/All requests.
New feature: Add fields (including SLA) to request view.
IE11 fix: .remove error
Added more field types to "My Request": textfields and textarea types.
- Problem showing portals when a portal was later removed from Jira.
- Problem showing field values when issue was shared in organization.
Added Priority, Fix and Affected fields to add requests on "My Requests".
Add CSS prefetching - such that uploaded *.CSS are instantly loaded when viewing the portals.
Fixed loading error when /jira path is not used
there was a problem with viewing the portal on a mobile phone. The widths has been adjusted, so that the left and right side bars are stacked if the window/mobile screen width is small.
fixed a bug where content did not render on portal pages
Changed name to "Design and Layout for Jira Service Desk".
Added separate option to design/layout the homepage, and the "other portal pages".
A small search box macro can be inserted to the "other pages."
The categories can now be ordered, which will be used to render the portals on the landing page.
Support for Jira 7.0.X and forward.
Load times better for landing page admin page.
IE11 bug fix.
As described in the description.
Go to Applications -> Service Desk -> Landing page customization to set up the landing page.