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
Jira Cloud does not have the ability for site-admins to be able to see the logs that the application. There is an existing feature request for this over in JRACLOUD-46206 : Provide the ability for Cloud Admins to access application logs. If you find this and just want to see the logs, then please watch/vote for that issue.
That said, if you're here because you have a problem like the one above, I would suggest that you create a technical support case with our Cloud support team. Our technical support team will have access to more logging of that application.
You can make this kind of request by going to:
Only site-admins, technical, or billing contacts on paid Cloud sites will have the ability to create such support requests. Admins of site on the Free plans can still complete this form, however they and other non-admin accounts from all site will have their questions directed here in Community instead for support per our Atlassian Support Offerings.
I hope this helps.
There is an audit log feature in Jira Cloud : https://confluence.atlassian.com/adminjiracloud/auditing-in-jira-applications-818578846.html could you let us know which specific info you would like to see which is not there ? Maybe it would be provided by the Audit log of Atlassian Access, but the ones in-products are already quite detailed imo
@Hermance NDounga - It's hard to say what information isn't there that we'd be looking for. Because this is cloud, we don't have full transparency into what's available like we would on server.
I can't necessarily speak for everyone, but basically if there's an error that pops up from bulk operations that has a vague (and not very helpful) error of "Please refer to jira logs for more details" we need to see those logs, otherwise there's no troubleshooting path available, and it may as well just say "error".
Alternatively, it could simply print the error(s) inline rather than, or in addition to logging it, which would prevent the need to find the correct log and then search through the logs.
For me, the ask is better error handling more so than an absolute need for accessing the logs. I'd like to know what issue(s) in the bulk operation failed, why, and (ideally) what steps I might take to fix it.
(For the record - I just ran this bulk operation that errored out - I checked the Audit log, and there's not been an entry for 2 weeks, so there's nothing for me to check. It appears to me that the Audit log that's available for our use is being used more for changes to the system/workflows/custom fields than for error logging.)