Assign default value to custom field ??

[Bunty]

Hello All,

We have a custom field called "Reason". In order for it to be available on the issue detail screen regardless of whether data has been added, it has to have a default value(None).

If the field is blank then it does not appear by default in the issue detail screen and we want to have it there for quick updating.

Thanks in advance,

Manikanta.

[Joe Pitt]

DO NOT ASSIGN A DEFAULT VALUE. People don't update fields when there is already a value. A manager forced me to do that and at the end of 6 months over half the issues had the default value of TBD when they were closed. 

[Nic Brough -Adaptavist-]

I agree with Joe on this.  Mostly.  There are some places where it is less likely to cause a problem.  The usual example is where a default is useful, but people will pay attention.  For example, setting a default priority of "trivial" - people will either accept it (in which case they mean it, or they obviously don't care enough about what they're raising for it to be important enough to raise it carefully), or they'll disagree with it and set a useful value.

But I've lost count of the number of Jira systems I've seen with huge swathes of utterly useless data caused by setting default values.  Text fields in particular.

[Bunty]

Hi @Joe Pitt and @Nic Brough -Adaptavist-,

I agree with both of you. But I want to add Text Field on Issue detailed screen with Test None. If the user wants to add any description in that box he will edit that Text field.

 Please, can one of you help me on how to add default field on the issue detailed screen?

Thanks Again,

Manikanta.

[Joe Pitt]

If you put a default value in the field it will appear in the detail screen and the user can edit it. You can't force the field to appear if there is no value in it.