Hi kforeman@atlassian.com : Is there any update on the fix?

kforeman@atlassian.com  – it's mid-December  – looking for my Christmas gifts and link to the communication plans

Hi 759955e045dd... Our engineering teams have been hard at work on this and we've identified a solution to archive old audit log entries. We'll be publishing some communications on our plans here in early-mid December. So stay tuned!

kforeman@atlassian.com is there any update on this one?

Kyle, I don't see much improvement after the fix for JIRAALIGN-6520 was released in 10.130. I just opened a new support ticket PS-169850 of the multiple timeouts I'm still receiving. Please help us with this, it's becoming completely unbearable to have such an unusable system change log.

Hi all,

In our investigation, we did identify an issue with the audit log date filters not applying on the initial load. We created the ticket below to track that work, and a fix is coming in the 10.130 release. We don't expect that this will resolve all of the performance issues and errors, we do expect it to resolve some of the initial page load errors that you were running into. But this ticket (JIRAALIGN-2642) will stay open to track the longer-term work.

https://jira.atlassian.com/browse/JIRAALIGN-6520 

-Kyle

Hi 2465a43636b0,

We have closed and re-opened this issue several times now, as previous improvements and redesigns only helped for a short term. Given that these issues are continuing, we believe we need to invest in changes for both the short and long term. So as soon as we have defined path(s) forward, we'll update the ticket's status accordingly. Until then, I think it's important that we avoid setting incorrect expectations.

That said, I understand the confusion about the status, given that we are actively investigating solutions. I'll add a note to the body of the ticket to make sure this is not missed (and so you don't need to scroll the comments to know that it is something we are investigating). 

-Kyle

@Kyle Foreman,

Thank you for the update. I know Atlassian is working on this based on your Backlog and prioritization polocies. 

But we see that its been sitting in the Long Term Backlog from 3Years. 

Hi all,

Our team is actively investigating both short and long-term solutions for this issue, as it likely will require a new architectural approach. I don't have more specifics to share at this moment, but wanted to let everyone know it is something we're actively working on. As soon as we've defined our path(s) forward, we'll provide another update. Thank you for your patience. 

-Kyle

Atlassian Team, 

For any Admin, Audit Log is the basic ability to get. We are not able to support users and understand changes made. 

Without this ability, There are  instances when we are left in the wind as to why the Aduit log issue is not resolved. 

I am sure that this is a global impact and many people have voted on this. 

Any reason why its in your LONG TERM BACKLOG even after so many Jira Align Admins have voted for this?{*}
{*}