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

Change External ID field when vulnerability is already in Faraday #506

Open
Aleridia opened this issue Jan 28, 2025 · 1 comment
Open

Change External ID field when vulnerability is already in Faraday #506

Aleridia opened this issue Jan 28, 2025 · 1 comment

Comments

@Aleridia
Copy link

Hi,

What's the problem this feature will solve?
We got vulnerabilities that are uploaded to faraday and then in an external ticketing service.
We can't update the "External ID" field on a vulnerability that is already in Faraday.

Describe the solution you'd like
The "External ID" field can be modified at any moment, with the possibility to make grouped changed for selected vulnerabilities.

When ticketing service is separed from Faraday and we want to push vulnerabilities in Faraday first.
Then when put the vulnerabilities in the ticketing service, we can't modify it in Faraday to keep our vulnerabilities baseline up to date.

Alternative Solutions
Put the external id in custom field.

Thanks in advance !

@ezk06eer
Copy link

Hello @Aleridia External-ID is supposed to be read-only by the user, in case of need it can be modified depending on the exported file prior to an import.

In case of need you can create your own id field using custom attributes.

Cheers!

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