-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
3
-
Issue Summary
As for the Current behavior, it doesn't seem to be possible to use Smart Values for Custom Field's Default Value Context.
As per the example below, when trying to set a Default Value for a Date Custom Field using a Smart Value, and even formatting the value, it fails
{{now.withNextDayOfWeek("TUE").format("d/MMM/yy")}}
| Custom Field Default Value with Smart Values |
|---|
 |
Steps to Reproduce
- Edit a Date Custom Field Default Value
- Add the Smart Values script above
Expected Results
The Smart Value being added to the Custom Field;
Actual Results
The Configuration fails, although the format being correct
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
- Closed
[JSWCLOUD-24504] Be able to use Smart Value for a Custom Field Default Value
Would also like to be able to use smart values within default values for field options inside Jira automations.
For example, when a manual trigger asks for manual input, be able to use a smart value in the Default Value field of the requested input.
Thank you for adding this feature request. 
It would be highly valued if we can have default value to a custom field as well.
Example usage: when user wish to get Temp access to a certain product, currently the date/time field is empty.
Apart from chosing 'Now" as default - all other date formats gives an error.
I would like to use smart values on custom field default values.
For example I want to add a prefilled link that contains issue key but it doesn't work that way. It still shows inside the link issue.key so instead I have to create issue without filling that field and then fill it with automation as automation supports smart values.
Agreed, could really use this for Jira automations.