![]() To see what I mean, here's an example that Atlassian themselves tout on their own documentation as a "ready for production" customer portal: I'm convinced this is purposefully hideous to force the purchase of plugins. While Atlassian's cloud offering is slowly playing catchup, Atlassian as a company has never quite seemed to nail down the importance of a friendly user interface, nor the importance of this when it comes to worldwide adoption. The answer lies within ease of use, but more importantly, presentation. This naturally begs the question: Why is JIRA Service Desk's pricing model roughly 1/10th of that of it's competitor? That's it, now you have a report with all the issues that belong to the specific queue selected.When it comes to SaaS products in the realm of Service desks, JIRA Service Desk is at the very least, just as powerful as the next solution (Zendesk comes to mind). Then, click Export.įinally, wait for the operation to finish and then click on the link to download your document. As you can see in the image below, you will have the Xporter option.įurthermore, you will be able to choose which queue you want to export, the report will contain only the issues that belong to the queue selected by you.Īfter clicking on the Xporter option, you will have a pop-up that will have a list of all templates available to use on this context, the export type format and the option that allows you to break a page when changing Issues, Projects, Issue Types or Components and an optional field to customize the file name of the report that will be generated. It must have at least one template configured with the scope Everywhere or Bulk Export.Īfter this, go to your Jira Service desk project and you will be redirected to the queue. First, you need to enable the option Xporter Service Desk Queue on the Xporter Global Settings screen. With Xporter you are able to export all these issues into just one report. This screen allows users to easily navigate and search all the requests. Jira Service desk has queues which contain all the customer requests that become issues. Then, click Export.įinally, the report can be downloaded and the document generated will have all the information from each request, in a single document. You will have a pop-up that will have a list of all templates available to use in this context, the export type format and the option that allows you to break a page when changing Issues, Projects, Issue Types or Components.įinally, you will be able to define a custom file name to the report that will be generated. It must have at least one template configured with the scope Everywhere or JSD Request List.Īfter enabling the option on the Xporter Global Settings, the Service Desk Customer Portal will have the Xporter option on the Requests section.įurthermore, click on the Xporter option. This feature will allow exporting all the requests created by the user, or the requests where the user is participant, into a single report.įirst, you need to enable the option, Xporter Service Desk Requests, on the Xporter Global Settings screen. It must have at least one template configured with scope Everywhere or JSD Request Detail.Ī new action will be available on Jira Service Desk actions section in order to allow you to get a document.Ĭlick Xporter - you should be able to select the template and the output format to generate the report. To get this working, enable the feature on the Xporter Global Settings screen. You can now get your requests printed on documents. Export from Customer Portal Request Detail
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |