You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Large companies run large volumes of projects across multiple teams. These tasks are often carried out in cooperation between various groups of specialists. That introduces the need to focus and operate on strictly defined data - in a secure way.
Jira Service Management users can utilize some pre-configured functions natively implemented in the Atlassian software. However, a palette of possibilities for such a solution does not offer broad usability. These default functionalities of Jira and JSM often require extension and personalization, especially in large companies. What is the alternative, then? 🤔
Queues for Jira Service Management app is the best choice to improve the effectiveness and security of an ever-growing set of tasks, tickets, and requests. That includes support for interdisciplinary teams working with Customer Portal. The app allows gathering, filtering, and displaying tasks in any venture in Jira on a single, conveniently managed screen.
As mentioned, it is essential when the teams deal with tasks scattered across multiple threads and projects. Collecting them into one centralized queue improves the work and reduces the need for switching between tickets. That allows one to control and manage all tasks in one place.
Such cross-project functionality is also helpful when managers simultaneously queue tasks for many teams - in business and software projects.
The Deviniti application enables companies and big corporations to put all projects in queues and arrange them in groups - in any number needed - creating a multi-level structure. A hierarchy significantly speeds up and simplifies task prioritization. It minimizes the risk of chaos and misunderstanding within undertaking ventures and makes them better organized and effective.
That is also the best way to save time, especially with proper task visibility. Managers and admins can restrict it to specified queues and strictly defined users. That makes navigating between listed issues much easier and boosts overall project performance. Tasks are carried out without distraction, only by people involved in a specific project - without searching the wrong queues. At the same time, the security within a given venture increases.
Among the crucial features, it's worth mentioning that the Queues app allows the creation of configuration backups using export to .json files. Restoring or importing a given configuration is also done via the JSON format.
The possibilities offered by the Queues application should also be extended with additional functions that will facilitate insight into additional information for external corporate clients (including those not using Jira) and enable them to export requests with such data. My Requests for Jira Service Management application will be of invaluable help here. The more so that MRE allows to edit requests on the client side.
An additional and equally helpful will be Issue Templates for Jira application. It enables automatic and, consequently, much faster-informing clients about work progress on their requests. It significantly improves the transparency of cooperation and, at the same time, increases the company's credibility. Next to in, the main functionality of the app is to support repetitive team work thanks to ready-made templates for Jira issues.
What do you think about such improvements? What are your experiences? Feel free to share and let us know if you already know the possibilities of the apps described above 👌
Oliwia Poświat _Deviniti_
Content and Community Specialist
1 accepted answer