It's all about the answers!

Ask a question

Ticketing integrated in RTC?


Mat Graetz (1123) | asked Jun 17 '13, 8:43 a.m.
Dear RTC community,

I am quite new here so please don't blame me for my "easy" question. 

Is there any solution out there that allows me to implement a ticketing system directly with RTC? I want clients to open tickets/service requests with a direct link to RTC work items.

Preferably totally integrated in RTC (e.g. Customer dashboard solutions etc.)

Thx for your answers!


Regards Mat

3 answers



permanent link
Mat Graetz (1123) | answered Jun 18 '13, 7:15 a.m.

Dear Ralph,

Dear Frederic,

Thanks for your answers. I ll check those options if they are applicable.

Regards Mat


permanent link
Frederic Mora (13811518) | answered Jun 17 '13, 7:44 p.m.
Mat,

We have implemented a ticketing system for our helpdesk folks using RTC. We use the simple process. The key is to create a project area with two separate user roles: "requesters" and "team members". Requesters are the users who can request some help. They can only submit a ticket (work item) and comment on it. Team members are the helpdesk techs and they have full access to the work items.

We created a custom field "Technical solution" which is just text and which is only modifiable by team members. It records the steps taken by the helpdesk to solve the problem.

It's helpful to have an LDAP user directory, so users can be imported in the project area as requesters without having to create an ID.

We slightly simplified the default workflow and removed an unnecessary state. A ticket can be in the Assigned, Open, Resolved or Closed state. A ticket is resolved when helpdesk proposes a solution. Upon user acceptance, it is closed. Only team members can transition work items.

You can use this article as a tutorial, it's quite complete: https://jazz.net/library/article/1003



Comments
Ralph Schoon commented Jun 18 '13, 3:42 a.m. | edited Jun 18 '13, 12:37 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Hi Frederic, thanks for mentioning the customization Article.
This might also be a good reference for customization:



The main content related to customization is in Labs 3 to 5. Currently there is no way to just run the labs 3-5 independently, but we are looking into how we can split the workshop in two parts.


permanent link
Ralph Schoon (60.5k33643) | answered Jun 17 '13, 9:02 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Mat,

this is by no means an easy question. In general you can use RTC for ticketing. Like on Jazz.net using https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWelcome you can allow your customers to create work items.

One of the issues with this is the openness of RTC. If you can tolerate everyone being able to see all requests, RTC is ideal. If you want to have customers isolated from each other and from the development team, you would have to solve some issues.

You can specify AccessGroups for RTC that can be used to allow only the Access Group Members to access specific work items. However there is no good automation that would help to automate assigning the access groups as far as I know. I assume you would have to create some kind of automation to do so. I have not thought about it really, so I am not sure which data you could use to group users by customers. Maybe you would have to implement some custom UI to submit the work item that also provides the customer information that you could use to set the access permissions.

In any case, you would have to have the user in the user database (e.g. LDAP) so probably have to have a special LDAP for CLM and the external users, otherwise they would not be able to log into RTC and the dashboard could could not be personalized.

You could use a special RTC instance where the customers have access and can create work items. Here you could use the access restrictions tied to the category for access management. This would require a team for each customer. The developers could link their work items to this one and work with data the customer would not be able to see in different project areas. The caveat would be that status updates on linked work items will not show up there. So the developers would likely top have to communicate with the customer using the customer's work item and would have to update it as well, if the work is done.

As you see, there are a lot of considerations around this dependent from how open you want to work.

Your answer


Register or to post your answer.