smart way to improvise workflows ! (workflows are a feature that are half developed and will be pushed once we complete the template migration)
Are you referring to “your custom” status or the “official” status (open / closed) ? you have “history” which will show every change on an item … but i think custom fields are not part of that history … so if you are referring to “your custom” status, probably you are right.
the change of status (again, this will only work for non-custom fields.
We would need to expand custom fields into the history logic.
https://github.com/eramba/eramba_v2/issues/1263 (internal ref)
I assume you refer to the “official status” now, correct the current notifications point to the “deadline” of the notification.
The notification is not an issue (int ref https://github.com/eramba/eramba_v2/issues/1264) , in fact we can plug the same logic to every section where we have a “status”
- (Risk|policy|compliance) exception
- Compliance Analysis Finding
- Security Incident
=== internal for eramba ===
Title: Risk Exception status update ($status to $status)
Description: Triggers when a Risk Exception status is changed from open to closed
Subject: same as title
The Risk Exception name “$name” has changed its status from $status to $status.
I understand out of this thread two features, notifications can be done for the next release. Custom fields into history will take longer, we need to complete the new template project first, but perhaps we can squeeze it as we have two other fetures requested for custom fields. Can really tell now.
thanks for the feedback!