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

Keep Findings as Default Tab for Report #405

Closed
er4z0r opened this issue Mar 22, 2024 · 2 comments
Closed

Keep Findings as Default Tab for Report #405

er4z0r opened this issue Mar 22, 2024 · 2 comments
Assignees

Comments

@er4z0r
Copy link

er4z0r commented Mar 22, 2024

Is your feature request related to a problem? Please describe.
Coming from the pre-4.1 release with an installed base and several users I can foresee acceptance problems when we have to tab to the findings tab every time a report is selected. My bold claim is: Most interaction the operators have with the report is when adding/editing findings. So let's make that as smooth and painless as possible.

Describe the solution you'd like
Either make "Findings" the default tab when opening a report or make the default tab configurable.

Describe alternatives you've considered
I wonder if including a "customizations.js" in the views would allow for better tailoring...

@chrismaddalena
Copy link
Collaborator

That's good feedback. I tend to agree with the assessment that the Findings tab is likely to be the most used. I'll make the Findings tab the default active tab. We can also experiment with returning you to whatever tab you last looked at, similar to how Ghostwriter remembers if you like to keep your sidebar open or closed.

@chrismaddalena chrismaddalena self-assigned this Mar 22, 2024
@chrismaddalena
Copy link
Collaborator

Added with 006da98.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants