You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 !
The text was updated successfully, but these errors were encountered:
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.
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 !
The text was updated successfully, but these errors were encountered: