So your 'could certainly be better' comment that is of most interest rather than what it can do :) Having come across some comments about the Jira portal I was interested to know if they related to older versions or if improvements had already been made. I do plan to look at the links and demos etc. Infrequent users will benefit from a simple, well-designed user interface. I would have thought portal functions are fairly standard across most ITSM tools, it will be how it is implemented that makes the difference. At the server side, JIRA must be installed before using it as end user. Our users are internal to the organisation, so we would rather they use the portal to report problems so it can surface self-help documentation to deflect tickets and prompt for capture of specific details which are often missed when users email in incidents. Installation at the Server Side JIRA follows the Client/Server concept. Let me know if you have any other specific questions that I might assist with in your evaluation. You might find this documentation useful - what-are-the-portal-and-help-center The client can transition issues such as resolve them if so configured.The client can make comments via email or the portal.The client can search for issues they have created containing certain text.It helps you quickly navigate and drill down into issues, schedule tasks and triage problems with drag-and-drop, accurately track time, work when you are offline. The client will be able to see issues that they are participants in depending on how the project is configured Jira Client is a desktop application for day-to-day work with Jira issues.The client will be able to see all of the issues that they have opened regardless of whether that was via the portal, an email, or if an agent open down there behalf.With that said here are some of the capabilities from the portal: In fact reality is that many of The customers that use our GSM projects don’t even use the portal at all. In my opinion the portal could certainly be better but it is fully capable of meeting most of my needs. Let me attempt to provide some input and point you to some documentation as well. In the future though JRJC may be extended to handle things like caching (conditional GET, metadata) or provide a higher level of abstraction on top of existing REST API - completely shielding the. I guess it depends upon your exact requirements for client side capabilities. It provides a domain object model of JIRA entities on the client side - objects representing issues, priorities, resolutions, statuses, users, etc.
0 kommentar(er)
