Issue Summary

Dependency: Adding a comment to a completed Dependency that has an affected Epic or Capability, reopens the Dependency and also marks the “Work is Done“ Field to “No” in the audit logs.

It works fine for a few Features and fails for some, but fails consistently for Epic or Capability. This is also reproducible in older JA versions. 

Steps to Reproduce

1. Create a new Dependency
2. Choose the “What is this Dependency for“ as “Epic“ or Capability
3. Now mark it as committed and then mark it done as well.
4. Add a comment and save.

Expected Results

Comment to be added and no changes made to the status or “work is set“ field.

Actual Results

• Comment is added, and the Dependency is moved from “Done” to “Committed”.
• The audit logs shows the change was made by user for “work is set“ field from “Yes” to “No”

Workaround

Currently there is no known workaround for this behavior.