WFA fields dont show Default values though they have defaults being set in config

[Nazia Tarannum]

WFA fields dont show Default values though they have defaults being set in config

[Nic Brough -Adaptavist-]

What do you mean by WFA field? What type are the fields that are missing defaults, and what contexts have you set up for them?

[Nazia Tarannum]

WFA fields=Fields on Workflow action/transition screen.

Dropdown/select list fields infact all types of fields are not showing defaults though they are configured.

Context is global for both issuetype & projects.

[Nic Brough -Adaptavist-]

Ok. Do the defaults on those fields work when you use "create issue"?

[Nazia Tarannum]

Yes, they do

[Nic Brough -Adaptavist-]

Ok, that means they're working.

Thing about a default value is that you only want to default it on issue creation.

During an issue edit, there is an existing setting for a field, even if that setting is "empty". The users have deliberately chosen that value, and you do not want to have a default override it. So default settings only apply on "create issue"

[Nazia Tarannum]

So nothing can be done for default values to appear after issue creation?

Issue that am talking is created programmatically using issueManager.createIssueObject()

Let me know if there is any alternative way I can show up default values in all screens.

[Nazia Tarannum]

If I use rest api to create issue it sets default values on issue creation itself but why not for jira api method issueManager.createIssueObject()

[SuhailM]

Which version of jira are u using?

[Nazia Tarannum]

• (v6.1#6144-sha1:2e50328)

[Nic Brough -Adaptavist-]

You don't really want to do it - that's why Jira doesn't do it.

If your users leave a field blank at creation time, then why would you encourage them to accidentally set it during an edit? It's blank for a reason.

If you do this, you'll find a LOT of your issues suddenly have defaults splattered all over them when you REALLY don't want it.