nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the Bets way to customize the issue layout for agents

Meir Ben Salmon

I am trying to change the layout that my agents are using to view and handle issues.

I understand that this is quite limited, so was wondering if someone can recommend on a good app that can address this issue.

Thanks

Accepted answers

All comments

Jack Brickey

Are you talking about Queues? “Best” is subjective and it largely depends on many factors that define how your team works. So a bit difficult to say but will give you my view...

if you have few agents then create a queue for each. You do t want too many queues.
you might consider queues by area, e.g. for IT JSD project: Network, PC, Phone, Employee Actions, etc...
in you queues include the fields that are useful to the agent, e.g. those that can be changed within the queue view, e.g. status, assignee
include the SLA field as leftmost column and sort by that field so that team/agent is focused on the ones that have or are about to breach
if you employee Escalation in your workflow then include a queue for this and place at the top

Meir Ben Salmon

Hi Jack

Thanks for the quick reply! i was actually referring to the actual layout of the page.

How does the page look, where are the different fields are located and how are they grouped...

Jack Brickey

I assume by page you mean the detailed issue view. That is really subjective. One way is to simply place the most used fields at the top and least at the bottom or even hide the least in the “more fields” area. Another approach is to group like field types: user fields, date fields, qualifying fields, etc.

I recommend interviewing your user base to find out what works for them.

Meir Ben Salmon

Thanks, Jack. yes, I am referring to the detailed issue view. However, I do not want to use the regular Jira layout where all of the fields are listed on the right of the screen, but rather change that so they are placed at the top and grouped by different titles.

Brands Miller

Navigation and account access design play a key role in how users interact with online platforms. References such as “https://kulabet.co.ke/login/” are often used to describe the entry point into user accounts where personal settings and activity are managed. The kulabet login structure demonstrates a standard approach where simplicity and clarity are prioritized in the interface. Clean layouts, predictable input fields, and secure authentication steps contribute to a more stable experience. Over time, users become familiar with these patterns, which reduces confusion and supports efficient access. A well-designed login system helps maintain continuity and ensures users can return to their accounts without unnecessary difficulty.

Brands Miller

gud

Austen Bernard

I tend to be skeptical of newer casino platforms because it takes time to establish a track record. What makes this one different is that the company behind it, UAB Nesė, has been operating land-based casinos in Lithuania since before online gambling was a major market here. That institutional background gives the platform a level of credibility that purely digital operators don't have straight out of the gate. The account registration process does require identity verification upfront, which some find inconvenient, but for a licensed platform it signals the operator is compliant with anti-money laundering obligations. The mobile browser experience mirrors the desktop version completely, including full access to live casino games. Twins Bet is the kind of operator that respects its regulatory obligations, which ultimately protects the players.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud