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
skalvaro opened this issue
Apr 19, 2024
· 0 comments
Labels
needs triageThis issue has been automatically labelled and needs further triageT: feature requestType: feature request. This issue is requesting a new feature
Is your feature request related to a problem? Please describe.
Not really a problem but on some MISP instances we don't need the sightings and pulling these takes up resources. Besides it seems odd to me that for Galaxy Clusters and Analyst Data we have the options to enable/disable the synchronisation on push and pull but for Sightings we only have an option to enable/disable on push, not on pull.
Describe the solution you'd like
An option to enable/disable Pull Sightings like it is done for Push Sightings.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
needs triageThis issue has been automatically labelled and needs further triageT: feature requestType: feature request. This issue is requesting a new feature
Is your feature request related to a problem? Please describe.
Not really a problem but on some MISP instances we don't need the sightings and pulling these takes up resources. Besides it seems odd to me that for Galaxy Clusters and Analyst Data we have the options to enable/disable the synchronisation on push and pull but for Sightings we only have an option to enable/disable on push, not on pull.
Describe the solution you'd like
An option to enable/disable Pull Sightings like it is done for Push Sightings.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: