{"id":17581,"date":"2021-07-27T10:00:00","date_gmt":"2021-07-27T08:00:00","guid":{"rendered":"https:\/\/www.xalt.de\/?p=17581"},"modified":"2025-01-14T08:43:42","modified_gmt":"2025-01-14T07:43:42","slug":"how-to-track-and-solve-user-problems-as-a-jira-admin","status":"publish","type":"post","link":"https:\/\/www.xalt.de\/en\/so-kannst-du-user-probleme-als-jira-admin-einfach-nachvollziehen-und-loesen\/","title":{"rendered":"How to analyze and solve user problems as a Jira Admin in no time at all"},"content":{"rendered":"

As your company's Jira admin, you're always getting messages from users who are having problems with their Jira. Sometimes you can't access a certain function, sometimes certain views and information are not available. However, it is then not always possible for you as an admin to understand what the cause of the problem is. The easiest way would be to see the problem from the user's point of view and be able to test live. There is an app for this in the Atlassian Marketplace. The user switcher<\/a>. <\/p>\n\n\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t
\"Viewing<\/figure><\/div>
\"Viewing<\/figure><\/div>\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t<\/div>\n\t\t\t\t\t
\n\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t\n\n\n\n

What is the User Switcher?<\/h2>\n\n\n\n

The User Switcher is an app for Jira<\/a> and Confluence, which allows you to connect directly to a user's account and view the Jira instance in its configuration and with its permissions. <\/p>\n\n\n\n

The app includes some security precautions. Firstly, it can only be used by admins. Misuse by other users is therefore out of the question. On the other hand, it is also possible that even admins cannot view certain user groups (for example, C-Level, IT Security, etc.).<\/p>\n\n\n\n

How does the User Switcher work?<\/h4>\n\n\n\n
\"Viewing<\/a><\/figure><\/div>\n\n\n\n

The app is integrated directly into your Jira and is accessed via shortcuts. For example, you type \"xx\" on your keyboard. Afterwards, a popup opens in which you can search for users and connect to the user. In addition, you can use the key \"who\" to display which user you are currently looking at. <\/p>\n\n\n\n

What are typical problems? <\/h2>\n\n\n\n

1. traceability of the problem for the Jira Admin not possible despite access and read permission<\/h3>\n\n\n\n

As an admin, you probably know it too. A user reports a problem with his Jira. For example, he can no longer view or edit a certain ticket despite access and read permission, although other tickets of the project can be edited without restrictions. <\/p>\n\n\n\n

Despite the exact description of the problem, it is not possible for you as a Jira admin to reproduce the problem. A problem search is then accordingly difficult. The solution in this case is to have the user's login data handed over to you (e.g. with a temporary password), which in turn would have data protection consequences. Or you would have to analyze and solve the problem together with the user via Zoom or on site. In any case, this would lead to additional time expenditure.<\/p>\n\n\n\n

2. dashboards are displayed incorrectly<\/h3>\n\n\n\n

Many Jira users always rely on their dashboard to get important information about tickets and projects. From time to time, however, important data is no longer displayed correctly for the user. <\/p>\n\n\n\n

As a Jira admin, this means laboriously putting together a JQL query to figure out why the dashboard is buggy for the user. Another approach is that the user shares the dashboard and the set filters with you, the admin. Only then it is possible to get more information and to analyze the problem deeper.<\/p>\n\n\n\n

The problem with both approaches, however, is that 100% accuracy cannot be guaranteed. This can only be ensured in this scenario if you connect to the user as an admin. The background here is that some information is only visible and released for the relevant user (despite admin permissions).<\/p>\n\n\n\n

Both scenarios reflect a similar basic problem: a Jira admin can only analyze and solve the problem with difficulty due to a lack of direct access to the affected account.<\/p>\n\n\n\n

The solution: User Switcher for Jira<\/h2>\n\n\n\n

The User Switcher for Jira allows an admin to connect to the account of the affected user at any time. This usually eliminates the need to quickly find the cause via complex approaches. Excessive time and effort is a thing of the past and you as an admin can take care of important tasks again. In addition, the administration is further simplified.<\/p>\n\n\n\n

User profile take over and data protection? - Is that possible?<\/h2>\n\n\n\n
\"Privacy<\/a><\/figure><\/div>\n\n\n\n

Maybe you're thinking to yourself: That's all well and good. But maybe I'm not allowed to connect to certain user groups. <\/p>\n\n\n\n

In all companies, there is a large amount of data that must not be visible to conventional users (including Jira admins). This applies especially to sensitive project data, financial data or even C-level data or IT security. <\/p>\n\n\n\n

In such a case it is possible to configure the user switcher in such a way that even admins can only access certain user groups. All others are then not visible for you as admin. <\/p>\n\n\n\n

This also ensures the data protection (and compliance) of your company and protects sensitive data from prying eyes.<\/p>\n\n\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Advanced Image Gallery<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Your secret weapon for a brilliant customer experience in your Confluence help center<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tTest it 1 year for free!<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Image\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"

Als Jira Admin deines Unternehmens bekommst du immer wieder Nachrichten von Usern die Probleme mit Ihrem Jira haben. Mal k\u00f6nnen Sie auf eine bestimmte Funktion nicht zugreifen, mal sind bestimmte Ansichten und Informationen nicht verf\u00fcgbar. Allerdings ist es dann f\u00fcr dich als Admin nicht immer nachzuvollziehen, welche Ursache das Problem hat. Am einfachsten w\u00e4re es, […]<\/p>\n","protected":false},"author":17,"featured_media":17595,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"categories":[37],"tags":[43,45,116,117,118],"department":[],"job_location":[],"start":[],"beschaeftigungsverhaeltnis":[],"class_list":["post-17581","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-atlassian","tag-atlassian","tag-jira","tag-atlassian-marketplace","tag-app","tag-plugin"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/posts\/17581","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/comments?post=17581"}],"version-history":[{"count":6,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/posts\/17581\/revisions"}],"predecessor-version":[{"id":17596,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/posts\/17581\/revisions\/17596"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/media\/17595"}],"wp:attachment":[{"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/media?parent=17581"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/categories?post=17581"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/tags?post=17581"},{"taxonomy":"department","embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/department?post=17581"},{"taxonomy":"job_location","embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/job_location?post=17581"},{"taxonomy":"start","embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/start?post=17581"},{"taxonomy":"beschaeftigungsverhaeltnis","embeddable":true,"href":"https:\/\/www.xalt.de\/en\/wp-json\/wp\/v2\/beschaeftigungsverhaeltnis?post=17581"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}