Why are new cards created with Resolution set to Done?

[Sean Klomparens]

I have 11 company-managed projects and am trying to get them all to use the same workflow: "SE Standard Workflow". We mainly use Kanban with a backlog.

Working: When issues are transitioned from Any Status to Done, the resolution is correctly set to Done, but can be edited further while in the Done status to Duplicate, Won't Do, etc. When the issue is moved back to the other statuses, it also clears the Resolution correctly (I added these post functions to all statuses except Done).

The problem lies with creating a new Issue. When created, it starts with a Resolution of Done and is put in the Backlog status. To quickly fix this issue, I have implemented a Clear Resolution All -> Itself as recommended on the best practices for resolution field article.  I have also tried setting a post function on the Create transition to clear the Resolution field:

Why does this configuration create issues that have a Resolution set to done?

Another thing I have attempted is creating a Resolution screen with the Resolution field, and associating it to the Workflow via a Default Screen Scheme using the Issue Operation "Edit Issue". This caused some of our added fields, namely Components and Fix Version to be uneditable or simply not appear when editing a card. It did resolve the issue of created cards having a resolution of Done, but I'm not sure exactly how it did this.

Note: we do not want a screen transition from Any Status to Done to set the Resolution. We want to default it to Done, but be able to set it to Duplicate, etc if it's a special case of Done resolution.

[John Funk · Accepted solution]

Hey Sean - Welcome to the Atlassian Community!

It definitely should NOT be setting the Resolution to Done on Create. Check the Create screen to see if the Resolution field is on it, and take it off. 

Are issues getting Cloned when the are created? Or some other method other than just the user clicking the Create button? 

[Sean Klomparens]

Hey John,

I don't currently have a dedicated Create Screen, I have a Default Screen with all the fields on it. Should I create a Create Screen and then also "Associate an issue operation with a screen" on the Screen Scheme page? 

Issues are being Created using the Create button at the top and Create button on the Backlog view, not using a Clone function.

Thanks for the help.

[John Funk]

You can have a single Default Screen - you just need to make sure the Resolution field is not on it anywhere. 

Either create a transition screen and add the field to it and then attach that screen to the transition to Done or simply set the Resolution in a post function on the transition to done. But it definitely should not be on your default screen. 

[Sean Klomparens]

I tried creating a Create Screen, and it worked! I did have to Associate the issue operation with the screen. I just copied my default screen, removed Resolution, and got it associated.

It feels like the behavior should never set Resolution to anything but cleared, even if there's no explicit Create Screen.

[Sean Klomparens]

The goal in the first place was to have the Resolution editable when it was in the Done status. Do you have a recommended better way of achieving this? 

[John Funk]

Well, bottom line is that the Resolution should not be on the Default screen at all! (Or Create/Edit/etc. You should do what is mentioned above, a new screen with just the Resolution field on it. Then attach that screen to the Transition to Done.