Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,295,002
Community Members
 
Community Events
165
Community Groups

Is there a way to get rid of the old Jira Align Logs which are not relevant today?

Edited

We have Jira Align and Jira Cloud integrated. The old error logs resurface time and again. It shows up Sprint errors for the old & closed program increments. Is it due to:

1) Jira Settings->Jira Setup->Sprint Start Date or

2) Running the sync via Jira Settings->Jira Integration?

Pls. suggest, if there is any solution / workaround to resolve it

 

1 answer

0 votes
Tom O_Connor Atlassian Team May 24, 2022

@Vinay Sharma 

There is not a way to clear out the logs.  

 

You can also view the log data within a selected time period, or search the logs for entries containing specific text in the entry’s details.

The logs also contain filters to further refine the items displayed. To apply a filter:

  1. Click the Apply Filters button.
  2. In the dialog box that displays, select your filtering criteria from the dropdown menu.
  3. To further refine the filter, click the plus (+) sign next to the dropdown menu to activate another field where you can add specific search strings to include in the filter.
  4. Click the Filter button to view the results in the log.

https://community.atlassian.com/t5/Jira-Align-articles/Reviewing-and-Understanding-Jira-Connector-Logs/ba-p/1253501#M52

Thanks @Tom O_Connor 

The issue is that because of the old Jira related issue i.e., Sprint was not started from a designated Jira board etc.. Jira Logs are resurfacing (getting re-created) time and again.

Since that issue happened in past, Jira logs should not resurface again and again reporting that old issues which are not relevant today. 

Tom O_Connor Atlassian Team May 24, 2022

This may be happening as JA is making API calls for sprints that are mapped, but no longer exist in Jira or are from the wrong origin board ID.  This could be happening when board sync are run to update any historic sprint assignments.  

Were you able to remove the old sprint mappings possibly?  

I suggest you open a support ticket so they can gather more details and information on possible solutions.  

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Align

Rockin' the Roadmap - How to make most of the Roadmap with Jira Align

The roadmap challenge for large scale agile enterprises Regardless of the agile framework you use, the agile enterprise has a massive scale with the challenge to connect hundreds of teams and thous...

2,513 views 7 24
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you