The first feature of note is the ability to import your assets from an external source, using CSV import. This was the most asked-for feature in Ephor. What you need to do is create a table of assets using your favourite spreadsheet, export the data to a CSV format, and import the CSV file to Ephor. This way, you can quickly migrate to Ephor from your legacy method of storing assets information.
Below is a screenshot of this feature:
PC Collector improvements
The PC Collector functionality, which uses Java-based computer scanner to collect information about user's machines and send them to Ephor, received a bit of a facelift. We've changed the way the scanner is launched - before, it used "Java web start" technology to launch an external Java application. This caused problems, especially on OS X where all applications launched from the web need to be signed in a way that made an optimal user experience quite impossible. So, instead of an external application, we're now using a Java applet embedded in Ephor web page.
You can see it in action on the screenshot below:
Restricted read-only Users
We've added a new user role to Ephor Standalone: "Restricted User". Restricted users are able to browse assets but only in read-only mode, which means that they can't modify contents of assets. However, they can still create JIRA issues and link them to assets - that way, they can report problems related to their equipment.
In Ephor for JIRA (and Service Desk), we've mapped the "Restricted User" role to configurable set of JIRA groups. This gives Ephor for JIRA administrator the ability to natively control who can edit assets.
Related to that, all Service Desk "customer" users are given the "Restriced User" role.
In addition, we've provided the ability to also restrict who can modify the "Asset" custom field in JIRA.
We've added the ability for every user to nominate one of your assets as their "primary" one. For example, you can make your main work machine "primary":
Primary assets can be quickly accessed from Ephor search page:
and also, in Ephor for JIRA, they can be quickly selected when filling in the "Asset" custom field:
In Ephor for JIRA, searching for issues (using JIRA's JQL language) associated with an asset was cumbersome - you had to know your asset's numerical ID. Now the support for JQL has been vastly improved. In addition to supporting numerical ID, we let the user search for issues using the full power of Ephor native search queries: you can specify things like your asset name, MAC address, IP address, owner, and pretty much anything else.
See this page for a full description of this functionality.
Support for JIRA Graphs
We've now made the Ephor for JIRA's "Asset" custom field "stattable" - which means that it can be used as data for JIRA graphs. This gives you the ability to plot graphs of the number of issues per asset.
See screenshots below for the preview of some of such graphs:
We're going to elaborate on the statistics support in Ephor for JIRA in subsequent releases, providing you with the ability to plot more advanced graphs, related to Ephor asset types and other criteria. Watch this issue for more details.