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
I have tested on Chrome and it works just fine. What is odd is that I can log into Atlassian using brave on different Jira accounts. I have tried deleting my cookies.
In the end the I had to navigate to https://id.atlassian.com, click the stop button so that I did not get re-directed to start.atlassian.com, then disable add blocking in brave. Finally after I did that it worked.
I think if the application cannot work with add blockers, there is something flawed with the design.
Hi, welcome to the Community!
Jira Cloud uses id.atlassian.com for authentication before passing your session back to the actual Jira site at your <site>.atlassian.net. Brave's Shield by default blocks cookies between domains. Since these are different domains, the Shield settings in Brave don't apply cleanly across the application - even if you've disabled Shield at one point, it takes a couple prods of Shield tweaking to get everything flowing well.
This isn't unique to Atlassian; I've reported this issue to Brave and noted many other sites reporting the Shield cookie blocker breaking IAM. It's notable that uBlock Origin, Disconnect, etc. don't have the same effect that Brave Shield does here. Hopefully it's sorted and "just works" soon.