Resolved Status for Issues: "Mark as done" vs. "100% complete"

[#1]

Description - WF defines the issue status Resolved as: a resolution was found and carried out for the issue. WF defines the issue status Closed as: no resolution could be found, but the issue is no longer a work item and, therefore, will be closed. Some issues can be resolved immediately, some are a gradual completion, some can't be resolved. If it's immediate, it makes sense/it's quicker to use the "mark as done" button. If it takes time, one can use the "% complete" bar, thus indicating to colleagues how far along it is and that it's being worked on; once complete, one sets it to 100%. In those cases, one would think the issue is considered a Resolved issue. 

Current Behaviour - However, "mark as done" results in a Resolved status, and 100% complete results in a Closed status. How does "100% complete" mean not resolved? Which is essentially what WF is saying. 

How would you like the feature to work - "Mark as done" and "100% complete" should both result in a Resolved status. If the issue can't be resolved, then the user can set the status to Closed or Won't Resolve.  

[#2]

@KristaTe If the user is part of a team you can set what status the "done button" uses. I didn't realize this when I first started but highly recommend editing all of your teams to have the same status settings for done and work on it / start.

[#3]

I have voiced this same argument a few times as some of our users have come to the same conclusion regarding the difference between status, percent complete and how to mark tasks/issues.

There seems to be too much differentiation between what was done, not done, done but not worked on, done but could not be done.  It's down right confusing.  

Rant aside, I agree with Monique's approach and would add training for your users to that. This however doesn't consider requestors, viewers who got edit/contribute rights to a task/issue. 

A change on this is strongly needed in my humble unexperienced opinion where Workfront is concerned or perhaps just more consistency across the board with regards to status.

[#4]

I agree with @D____D! One other thing I did to help combat this confusion was hide many of the status options for issues and then bulk edited the existing status on completed issues. Normally I'm against creating custom statuses or editing the existing ones, but this may be a good case to rename them to exact what you mean. "Cancelled"; "Done"; etc. You could also add a custom field to the form with more specific details to capture what could have been done and possibly why it wasn't.

I think this may be able to hold us over until Adobe can make things more consistent.