Topics Map > JIRA

DoIT Shared Tools - JIRA - Login and Access Troubleshooting

This document describes why common login issues occur and how to resolve them. If you continue to experience issues logging into DoIT JIRA, please contact the DoIT JIRA Admins via the DoIT Help Desk.


A reminder of the discontinuation of Atlassian Jira and Confluence,DoIT Jira and Confluence Service Change - Timeline and Roles & Responsibilities

Login Cycling Error

If you are able to log in directly to JIRA but are unable to log in when following a project link, it is likely that you do not have access to view the project.

If you continually bounce back between JIRA and NetID login screens when following a specific project link, please contact the project administrator to request access.

Timed out of JIRA after only 5 hours

DoIT JIRA uses Apache Tomcat, which is a server and JSP/Servlet container that handles both static and dynamic pages. The static pages are generated using HTML. The dynamic pages are generated using Servlet and JSP.

Apache Tomcat has a maximum session time of 300 minutes (5 hours). If you are on JIRA with work in progress and exceed the 5 hours, your session will time out and you will lose your work. You will also be led to an unfamiliar screen to log back into JIRA. This document,  DoIT Shared Tools - JIRA - Unable to Login to JIRA/ Led to Unfamiliar Screen , will help you to get back onto JIRA.

Inactive Account Troubleshooting

If you once had access to JIRA and are repeatedly seeing an error that your information is incorrect, it's likely that your account was inactivated. This document reviews the deactivation of users in JIRA due to the lack of their activity.

How can I tell if my account has been inactivated?

Users who have previously accessed JIRA should be prompted to select their campus via the Wisconsin Federation page.

However, if you are prompted to log in again or get an error that your credentials are incorrect, it is likely that your account has been automatically inactivated.

Why do JIRA accounts get inactivated?

JIRA accounts get inactivated because either:

  • Your UDDS has changed since your last login and you are now locked out of JIRA from multiple tries due to the UDDS mismatch

  • You have not logged into JIRA in the past year and your account was inactivated due to DoIT JIRA's limit to 2000 user licenses.

Auto-inactivation does not alter any of the settings or data relating to the (inactivated) user.

How do I regain access to my inactivated JIRA account?

If you suspect that your account has been inactivated, please contact st-help@doit.wisc.edu to regain access.

UDDS for group management discontinued

The Jira authentication plugin is no longer supported. So in order to upgrade Jira, the Jira team implemented a new authentication plugin the week of August 15, 2022.

As a result of this change, Jira group management using UDDS codes was discontinued (UDDS stands for “Unit, Division, Department, Subdepartmentâ€Â). This functionality was previously custom developed and is associated with the old plugin.

How the UDDS change this affect the use of Jira?

  • The majority of Jira users will experience minor changes in their user experience.
  • Groups and projects that do not manage Jira groups using UDDS codes should not be affected.
  • Groups and projects using UDDS codes to manage Jira groups will need to follow the new process for managing team and staff changes.
  • Please review this article





[Doc 116329 content is unavailable at this time.]


Keywordscan't log in unable inactivated deactivated lost access lose udds locked out asked change password still can't get changed net id netid incorrect cycle cycling loop time out kicked out   Doc ID58509
OwnerJohn H.GroupShared Tools
Created2015-11-25 09:51:40Updated2024-02-15 11:13:33
SitesDoIT Help Desk, DoIT Staff, Shared Tools
Feedback  0   0