Currently, when adding a New Task to an existing Incident, you must manually fill our all of the task fields. Most of our tasks are already pre-defined. It would be great if we could select on of our pre-defined tasks to add to the Incident.
I am currently on leave during Jan 29-31 2020.
Please call me if you are urgent or I will reply your email when I am back.
Happy Chinese New Year
I think that would warrant a separate Idea.
The analysts focus during incident response won't be the same as the designers focus when building a library of tasks. Seems like ad hoc tasks added this way would require some further review and acceptance or duplication, proliferation, etc could become an issue.
I would actually like to see this taken a step further, and if a task is constructed on the spot, be able to add it to the regular task lineup for future use.
Also give the ability to do it via the internal scripting module
Ooops. Please see my full size example of what this could look like in the UI.
A related Idea would allow the ability to add whole "Plays" from your Playbook. Essentially a collection of Tasks, Fields, Logic.
I completely agree with the original requester.
As an analyst I would like the ability to add a pre-defined Task to an Incident I am working on that may not originally be in scope of the incident. For Example, these Tasks could be for containment/eradication/recovery.
This would allow for truly dynamic playbooks as the Analyst would have the ability to essentially "build their own" playbook as the incident unfolded to best suit the needs of the situation while following the Dynamic Playbook originally "called" for this Situation/Incident.
See my attachment for a visual example.
You won't be notified about changes to this idea.