[Feature Request] Status and owner for observations in report · Issue #601 · GhostManager/Ghostwriter · GitHub
More Web Proxy on the site http://driver.im/
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
Is your feature request related to a problem? Please describe.
It would be helpful when drafting a report to track their status and the user responsible for the attached observation. This would be similar to how findings already have a status and owner.
Describe the solution you'd like
Provide a way to assign observations to a user and mark its status.
Describe alternatives you've considered
Currently, I use the observation title to track this. For example, I'll do something like "[sean] Some observation title" when it is assigned to someone and needs editing. When the editing is complete, I remove the "[sean]" so that the title is clean.
Additional context
This may be due to our team treating observations as less static than originally intended. For some of our observations, they are just dumbed down findings with some editing or populating of project-specific data; in other words, we found the simpler title and description easier than the large number of options available for a finding.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It would be helpful when drafting a report to track their status and the user responsible for the attached observation. This would be similar to how findings already have a status and owner.
Describe the solution you'd like
Provide a way to assign observations to a user and mark its status.
Describe alternatives you've considered
Currently, I use the observation title to track this. For example, I'll do something like "[sean] Some observation title" when it is assigned to someone and needs editing. When the editing is complete, I remove the "[sean]" so that the title is clean.
Additional context
This may be due to our team treating observations as less static than originally intended. For some of our observations, they are just dumbed down findings with some editing or populating of project-specific data; in other words, we found the simpler title and description easier than the large number of options available for a finding.
The text was updated successfully, but these errors were encountered: