Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data is off by 1 column when exporting open findings to an excel file #10012

Open
2 tasks
revaspeho opened this issue Apr 23, 2024 · 0 comments
Open
2 tasks
Labels

Comments

@revaspeho
Copy link

Be informative
Please enter as much information as possible, otherwise we can't provide support. If possible upgrade to the latest release or dev version and try again.

Hi DefectDojo team, I am trying to export open findings to an excel file. I am noticing that data for some of the columns appears to have shifted to the left by 1 column. The csv export appears to be working correctly. Comparing the two exports, it seems that the excel export shifts the data 1 column to the left on the "finding_group" column. For example in the service column, I see the severity rating (e.g. MEDIUM, High) instead of service name. Can someone help me look into this? I am currently on version DefectDojo version 2.32.0.

Bug description
Data is off by 1 column when exporting open findings to an excel file

Steps to reproduce
Steps to reproduce the behavior:

  1. Go to open findings
  2. Click download icon and select Excel Export
  3. Click download icon and select CSV Export
  4. Compare CSV export and excel export. Should see excel export reporting data incorrectly where data shifted to left by 1 column

Expected behavior
CSV and excel reports should be the same.

Deployment method (select with an X)

  • Docker Compose
  • [ X] Kubernetes
  • GoDojo

Environment information

  • Operating System: [e.g. Ubuntu 18.04]
  • DefectDojo version (see footer) or commit message: [use git show -s --format="[%ci] %h: %s [%d]"]
  • DefectDojo 2.32.0
  • AWS EKS cluster: 1.28

Logs
N/A

Sample scan files
N/A

Screenshots
N/A

Additional context (optional)
N/A

@revaspeho revaspeho added the bug label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant