Servado Enterprise Portals can display Jira issues in a tile to end users. This is accomplished by using the Issue Info action command but first a tab needs to be created, then the tile can be added to the tab. Once a tab has been created, the action tiles for this tab can be created. That is done by clicking on the green Add New Tile under Tiles:
Later on, once more tabs have been created, administrators can re-use tiles from other tabs by clicking on Import Tile.
The action command that we want for this example is Issue Info.
Then a configuration area like the one below will appear. The following configuration needs to be done in the top half of the configuration area:
Tile Tile: Give the tile a name, end users will see it displayed in the portal
Tile Description: Write a description, optional
Tile Icon: Choose or upload a icon for the tile
Slide the Visible lozenge to the right (make it green) so the statistical graph will be visible in the portal
In the lower half of the, we need to give the JQL query a name in the Label area (in the example below it is called Open Issues). Next the JQL itself is inserted into the area below. This JQL is in fact a regular Jira Query Languge (JQL) just as is used in Jira. We recommend writing the JQL in Jira to test and fine tune to your needs. Below the JQL are are then addtional options:
It is recommended to consider the target audience of the issues and tailor the JQL accordingly, for example by using Issue Security Level and/or claims of users to limit issues selected, see examples of jql filters
And finally click on Save to save the tile. Clicking on Apply will save the configuration but keep you on that page. Note that you can use ORDER BY to order your JQL according to your needs.
Multiple JQL´s can be added in the same tile and they will appear as seperate tabs:
Just click on the Add JQL button to add more tabs to your Issue Info tile:
And don't forget to save after you have configured it all clicking on Save Tile.
Note: Servado will only display maximum of 500 issue per tab, to prevent performance degradation of the system.
Here you can see how the above configuration appears in the Portal:
From version 2.0, Servado has offered the capability of allowing end users to be able to move a ticket through a workflow, for example approving a change or IT purchase. This can be very useful when an approving manager does not use Jira on daily basis or does not have a Jira license.
This is configured by clicking the box Allow workflow transition:
Then a new sub-section will open up. In this sub-section, the first thing you need to do is to choose the workflow you want the end user to participate in. Click on the box to choose. Then click the Allow box next to the transition you want to make available. Then give the transition (button) a name in the Field Label. And finally, if you want to limit who can perform this transaction, then you need to click on the lock that is to the far right of the transition:
The limitation (lock) uses claims filter to limit who can perform the transition (i.e. see the button). The following window appears once the lock icon is clicked. Fill out the claims filter you want to use (in the below example, only the user with email firstname.lastname@example.org can see the transition button). Then click on Ok:
And finally, do not forget to click on Save to save the whole configuration.