Support

There is no module for My Tickets. When thinking about it we concluded that the information would be too dense to display in a module or it wouldn't be adequate. What I mean is that if we displayed all information in My Tickets you'd have too much information to fit in a module. If we only showed the ticket title and last response time it would be very much out of context since you couldn't tell the status of your ticket (Open, Pending, Closed, ...), who last replied to it (was it you or a member of the staff) or even which category it was filed in.

If you give me a use case I might be able to understand better why you need it and add it to our to-do list if it's something we can reasonably work out.

Regarding New Tickets, it can't really be made into a module. The interactions required to file a new ticket form don't translate very well to what is reasonable to do in a module. The best approach is to create a Custom module with a button pointing to the New Ticket page for the category that is most appropriate for where it's going to be presented. This is the approach we use on our own site when you view the tickets in a category. When you scroll all the way to the bottom we have a Custom module which shows a button to open a new ticket in the current category. It's literally a different module for each category.

I wouldn't personally use a page builder for this page. It's redundant, it's slow and tends to get in the way every time you upgrade your site. Using Joomla core features is a far superior solution in all respects.

Solution A. Login module and a prayer (easy, not as polished)

Create a menu item which leads directly to the New Ticket page in Akeeba Ticket System.

Publish a login module in the ats-mytickets-top position which displays at the top of the New Ticket page. Set its access to Guest so it only appears to non-logged-in users.

I also recommend publishing a Custom module in the same module position with some text explaining why you need to log in to file a ticket.

The custom module positions are explained Akeeba Ticket System :: Custom module positions in the front-end. When creating a module you won't see them in the drop-down of module positions BUT you can type them into that field anyway.

The downside of the approach above is that if you have no publicly accessible ticket categories the users see a login dialog and below it the new ticket interface with no support categories options. There is, of course, a way to implement a better flow.

Solution B. Smoke and mirrors (marginally more involved, more polished)

Create TWO menu items called New Ticket.

First menu item is of type Users, Login Form and its access is Guest. In its Options tab set the “Menu Item Login Redirect” to the second menu item called New Ticket.

Second menu item is of type Akeeba Ticket System, New Ticket and its access is Registered.

What happens is that both logged out (guest) and logged in users see the New Ticket menu item. Logged out (guest) users clicking on it are taken on a login page which redirects them to the actual New Ticket page upon successful login. Logged in users (Registered) clicking on New Ticket see the actual New Ticket page.

You can use the same trick for the My Tickets page or, in fact, any kind of page you want to hide behind a login wall.