Project lead not getting assigned to issues

[Deleted user]

When creating an issue, we´ve set it so that the project lead gets assigned to the issue automatically. Recently it gets assigned to one of our administrators and not the project lead.

What needs to be done so that the "Spoc" gets automatically (without automation seetings) assigned to the issues?

Thank you in advance!

[JamieA · Accepted solution]

The resolution field is intrinsically related to your workflow, so it doesn't make any sense to put it on an edit screen. All of your states should either map to resolved (possibly a specific resolution) or to unresolved. If that's the case you should only put it on a transition, or unset it using a post-function, from closed -> open for instance.

The worst possible idea is to create a resolution called Unresolved. More info here which is still not out of date: http://blogs.onresolve.com/?p=84

[Reza Khosravi]

Hi @Vishnu,

Resolution is a SYSTEM Field and it's always required, you cannot make it optional from Configuration scheme. 
Based on what I find in atlassian, it's better to not have "Resolution" in edit screen and try to change it through the transitions.

[Vishnukumar Vasudevan]

Hi,

I think you need to look in to the 'Field Configurations' for this issue type. You might have set 'resolution' as required there.

So the fix is, make it 'Optional' there and use validators to have resolution mandatory in any transitions.

Thanks, Vishnu.

[Gurpreet]

@Vishnukumar Vasudevan he is talkign about resolution field bro. it is a built-in field and you CANNOT set it to optional. please read the question carefully before posting. thanks

[Nic Brough -Adaptavist-]

Nope.  It's optional in the field config.

Have another read of the question - the first sentence is correct (still - you're posting on a 6 year old question!).

[NielsJ]

Usually we have a transition named "Re-Set resolution" or so in the final state of our workflows. On the transition screen you can only modfy the resolution and add a comment. So you never get "trapped" ;-)

Another idea might be to add a Validator to your final workflow steps that define the resolution as a required field.