No login possible in Tools/Tasks/Servers with same credentials, but different IDE projects

Hello, Thorsten Schoening. Please accept my apologies for the inconvenience.

Could you please collect the IDE logs (Help | Collect Logs and Diagnostic Data), share them using the JetBrains Uploads service, and write here the ID you receive? From the description and the part of the log you shared, I suspect the issue could be the same as described in this bug report; I want to check the full log to be sure I'm not missing something. 

Upload id: 2024_01_12_y7mkzn5d6kxB6Vp4nPpezs (file: idea-logs-20240112-1402597162225424918089201.zip)

Thank you for sharing the logs. Unfortunately, the error message reported there is the same as in the IDE UI:

2024-01-12 14:02:12,869 [  15704]   WARN - #c.i.t.i.TaskManagerImpl - Cannot connect to JiraRepository(URL='https://veda-group.atlassian.net')
java.lang.Exception: Login failed. Check your email address.
	at com.intellij.tasks.jira.JiraRepository.executeMethod(JiraRepository.java:324)
	at com.intellij.tasks.jira.rest.JiraRestApi.findTasks(JiraRestApi.java:56)
	at com.intellij.tasks.jira.JiraRepository.getIssues(JiraRepository.java:127)
	at com.intellij.tasks.TaskRepository.getIssues(TaskRepository.java:154)
	at com.intellij.tasks.TaskRepository.getIssues(TaskRepository.java:159)
	at com.intellij.tasks.impl.TaskManagerImpl.getIssuesFromRepositories(TaskManagerImpl.java:867)
	at com.intellij.tasks.impl.TaskManagerImpl.doUpdate(TaskManagerImpl.java:825)
	at com.intellij.tasks.impl.TaskManagerImpl.lambda$updateIssues$15(TaskManagerImpl.java:819)
	at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:249)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:840)

Is it possible to check the error on the server side? Also, could you please try to set up a new token and see if the connection using it performed successfully?

Is it possible to check the error on the server side?

No, Atlassian is hosting things and I don't have any permissions.

Also, could you please try to set up a new token and see if the connection using it performed successfully?

Already tried that multiple times with multiple different new tokens. All of those failed in the IDE project I'm trying to newly configure and all of those succeeded in the formerly already configured projects.

It's like if this one IDE project instance is blocked for some reason or something. But is there any difference between the projects at all? Is there some different client-ID sent or is Atlassian otherwise able to distinguish the different requesting projects somehow? Theys all run on the same hardware, Windows etc. I just switch between working and non-working projects.

Thorsten Schoening, thank you for the update. 

I created a corresponding bug report in our YouTrack; please consider upvoting it to receive updates.

Just out of interest I deleted the formerly created server, re-created it and logging in to JIRA works now. I'm very sure to have the exact same settings like used before, but I'm not too sure if I really removed the entire server setting in the past or only cleared the input values. Anyway, removing the entire entry and starting from scratch worked right now and might be a possible explanation why it worked for some collegue with the same problem as well. He might have removed the entire entry at some point as well.

Though, it's not only time-related! Before removing the whole entry I used the test button and things still failed.

Thorsten Schoening, thank you for sharing the update; I'm glad the problem is solved now! 

I'll add this workaround to the issue description so if other users encounter the same problem they could find and use it. 

In case it helps anyone else, and maybe the developer handling the bug, if you still can't make it work with the suggestion above, the issue is with selecting the “Use personal access token” checkbox. If you delete and recreate the server, and check this box, it won't work. The same error about checking your email will show. However, if you don't select the box, and just put in the server URL, it will be automatically detected that the server needs a token rather than a password, the text inputs will change accordingly as if you had checked the box, and the connection will work. This also explains the issue Thorsten Schoening was having. It's the exact same data, but it works in one scenario and doesn't work in the other one.

Ahmed Felix thanks bro for this workaround. I have come across this issue and was losing some hair over it. Your workaround worked.