How to set default value for a dropdown field without reconfiguring context options

[Alex Barker]

We have a global "assigned team" field that has options which are the same across ALL projects. However, the default value of this field should be different across projects.

I ran into these problems when trying to accomplish this:

• Using field contexts mean that the options need to be manually copied (no doubt will break something) for each different default value we want.
• Using automation means that the field isn't filled out when the issue is created.
• Default value on request forms is for service projects ONLY, we want to use this on software projects too.

Is there a way to set the default value without the problems listed above?

[John Funk]

Hi Alex,

What if you hid the field in your form for that project (leave it on the Create screen and Edit/View screen) and put the default value in there? The user would not see it at create time, but immediately when it is created it should be seen. 

[Hans Polder _Devoteam_]

@Alex Barker ,

I think Automation is your best bet in this case. What are your objections to having to wait a couple seconds after creation until the field is filled? This should not take much longer than that.

[Alex Barker]

Yeah, automation is what I currently have set up and it's not too bad.

It's only a problem when users are filling out the field initially, since the default will not be there until after submission. Just a bit confusing for users is all, would be nice to have it filled out by default and then users can select a non-default value if applicable.

Thanks

[Hans Polder _Devoteam_]

Hey Alex,

I would remove the field from the CREATE screen(s) in that case. If you only have it present on the EDIT/VIEW screens, it will be editable by Automation, but not be able to set during creation by users.