I am resolving this issue as "Answered" since I did not hear any further response after my last comment. We've improved the documentation around how the Done resolution is used with Simplified Workflows.

We will not be enhancing features around the choice of the resolution at this time.

Regards,
JIRA Agile Team

Thanks for reporting this issue.

There are two scenarios which involve the use of the "Done" resolution in a project which is using Agile Simplified Workflow:

1. An existing project has its workflow simplified

During this process, the administrator is asked which statuses will set the resolution to "Done". Currently they are not asked if "Done" should be a different resolution.

Once the workflow has been simplified, a new workflow has been created specifically for that project. Once this happens, you can use JIRA's Workflow Editor to modify which resolution is set for the statuses desired.

2. A new project is created from Agile

Since this is a brand new project, it is reasonable to expect that administrators do some additional manual configuration (such as setting the resolution on desired statuses) before the project is used.

Given that the Workflow Editor allows setting the resolution specifically, what else would you like to see happen?

Regards,
JIRA Agile Team

So, now I know this resolution is added if/when you use the Agile Simplified workflow. So, I agree that you should get to pick the resolution instead of the system creating one called "Done" if it does not exist.

This happened to us after 6.1 and it is in fact causing confusion because we don't want, and never wanted to use a resolution with a generic name like "Done". What I don't understand is what triggers Agile to create the new resolution and how do you prevent it? Agile should at least let you map the resolution to an existing one that you want to use instead of just creating a new global resolution.

From what I am reading, this happens when you "create a project" using Agile (or Agile Project Template) but I don't know what that means. We normally just create projects the standard way. How do you use Agile to "create" a project?

I'm guessing the "Done" resolution was added in 6.1. As you know, the list of resolutions is system-wide across all projects and all issue types. There’s no way to tell Jira which resolutions are valid for which issue types and no way to restrict certain resolutions to specific projects. I administer a large Jira instance with several hundred projects that collectively have about 50 different issue types. I REALLY don't appreciate having another resolution value created without warning. It was not made clear in the release notes that this would be happening and we didn't catch it in our testing. As a result, there were several hundred issues using the new resolution before we even became aware of it. So now we have to either clean up the hundreds of issues that are using the new value or try to explain to several thousand users how the "Done" resolution might or might not apply to their issue type.

Or make it convenient to restrict a workflow to a set of Resolutions depending on issue Type. I suggest Resolution Scheme to map a set of valid resolutions to an Issue Type and Workflow. This can be done by tweaking Workflow Properties https://confluence.atlassian.com/display/JIRA/Workflow+Properties but it needs to be a better UI to use well.

From https://answers.atlassian.com/questions/121052/resolution-fixed-vs-resolution-done-what-is-the-difference