We use Wrike extensively for incident management and for the long-term documentation of processes related to NIS2 and other regulatory requirements.
The following enhancements would significantly support our work:
1. Categories and folders for attachments
It should be possible to categorize attachments within a task or project or organize them into custom folders.
Security incidents often generate a large number of supporting documents, logs, emails, and other files. A structured filing system would help users maintain a clear overview and quickly locate the required information later.
2. Change history for custom fields
We would like to have a clear change history for custom fields. It should show:
- which field was changed,
- when the change was made,
- which user made the change,
- the previous value,
- and the new value.
This information would be very helpful for maintaining traceability and documenting security-related incidents.
3. Additional email recipients when replying from a task
When replying to an email from within a Wrike task, users should be able to add further recipients in the “To,” “CC,” and, if applicable, “BCC” fields.
This would allow additional contacts or managers to be kept informed about the progress of an incident without having to send a separate email outside Wrike.
4. Locking or protecting completed tasks
Once a process has been completed, it should be possible to lock the corresponding task against further changes. Possible options could include:
- completely locking the task,
- restricting changes for specific user groups,
- password protection,
- or allowing the task to be unlocked only by authorized users.
This would help prevent completed documentation from being changed accidentally or information from being deleted. This would be particularly useful for maintaining the long-term traceability of security incidents.
5. Changing item types through automation
Wrike automations should be able to change the item type of a task.
Within our incident management process, we distinguish between:
- incidents created manually through a request form,
- tasks created automatically by external systems,
- and incidents received through the email integration.
Automatically changing the item type would make it much easier to classify and process these incidents correctly.
6. Complete export of projects and tasks
We would like an export function that allows a complete project, including all related content, to be exported. Users should be able to select which components are included:
- project information,
- tasks and subtasks,
- descriptions,
- custom fields,
- comments and activity history,
- attachments and documents,
- assignees,
- status information,
- timestamps and change histories.
PDF and a complete export archive would be particularly useful output formats.
In some cases, we still share project documentation in printed form. A print-ready export of an entire project would therefore be very helpful. At the same time, a complete export could be used to archive completed incidents and provide evidence of the associated documentation.
From our perspective, these enhancements would significantly improve Wrike for incident management, long-term documentation, and structured record-keeping.
