Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,456,701
Community Members
 
Community Events
176
Community Groups

Time Submission Metrics export not functioning properly

When attempting to export data using the Time Submission Metrics export on the Time Tracking->Reports page, the data exports as a corrupt .xls that returns the following error when attempting to open (pic 1 attached). When referencing the error log listed, this is the contents of the log: 

"XML PARSE ERROR: Missing end-tag
Error occurs at or below this element stack:
<ss:Workbook>
<ss:Worksheet>
<ss:Table>"

Note that with multiple attempts to export in a row without changing parameters, the file size seems to randomly differ (pic 2). Previous workaround for this issue was to split the export into smaller date ranges and manually combine the files, but this no longer works and now delivers the same error.

 

pic1.PNGpic 2.PNG

1 answer

1 accepted

1 vote
Answer accepted
Mark Cruth Atlassian Team Sep 07, 2021

Hi @Karl Pfeiffer! Thanks for reaching out! Unfortunately I don't think we'd be able to troubleshoot this very well on community (based on what you shared, it definitely looks like it could be a bug). I'd recommend submitting a support ticket to:

https://support.atlassian.com/contact/

This way a support engineer could help you troubleshoot and resolve your issue. 

Hope this helps! 

Thanks Mark, will do

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events