Issues
- 0
- 0
As a user, I want to easily crawl a website's new path
#292 opened by lm-sec - 0
- 0
As a user, I want to launch a job on multiple targets from the Launch jobs page
#290 opened by lm-sec - 0
Orchestrator fails when resource quotas do not exist
#285 opened by Aboisier - 0
As a user, I want to filter the ports by service
#276 opened by lm-sec - 0
- 0
As a user, I want to export my data
#274 opened by Aboisier - 0
As a user, I want to see data from a single project
#273 opened by Aboisier - 0
As a user, I want a better way to visualise websites
#232 opened by lm-sec - 0
- 0
- 0
As a job implementer, I want more dependencies in python job containers by default
#269 opened by Aboisier - 0
- 0
As a user, I want to create a job from a template
#236 opened by Aboisier - 0
- 0
- 1
As a user, I want to customize my job containers
#222 opened by lm-sec - 0
Tags do not look as good as they used to
#253 opened by lm-sec - 0
- 0
Editing a user's role is not working
#257 opened by lm-sec - 1
As a user, I want to see when my custom job prints to stdout, even if not in the expected findings format
#188 opened by lm-sec - 0
As a user, I want a more flexible tagging feature
#256 opened by lm-sec - 3
- 0
- 0
- 0
- 0
- 0
As a user, I want to see the resource usage of the stalker-jobs namespace in the dashboard.
#252 opened by lm-sec - 0
- 0
- 0
- 1
- 0
I want to search through the doc
#235 opened by Aboisier - 0
As a user, I want all jobs to be visible and editable
#217 opened by lm-sec - 0
- 0
- 0
As a user, I want to pin resources to the dashboard
#231 opened by lm-sec - 0
- 0
As a user, I want to be able to inject secrets as a job parameter, without every user seeing them
#203 opened by lm-sec - 0
As a user, I want to filter the past job executions
#229 opened by lm-sec - 0
- 0
- 2
- 0
- 0
As a developer, I want job tests to run in the CI
#208 opened by Aboisier - 0
As a user, I would prefer reading and entering a more human-like format in the subscription cooldown field.
#194 opened by lm-sec - 0
- 1
As a dev, I want my PRs to fail if my files do not respect the proper naming conventions
#178 opened by lm-sec - 0
As a dev, I want to automatically know if every Flow Manager route are tested for authorizations
#179 opened by lm-sec