Actions
Feature #7520
openDynamic default value for custom fields
Status:
New
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
2011-02-02
Due date:
% Done:
0%
Estimated time:
Resolution:
Description
When we create a new custom field, it's possible to put a default value corresponding to datatype.
We can currently only put a constant value inside.
I wonder if it could be possible to have instead a sql query inside for example or an empty ruby script generated systematically.
Each time a new issue is created (example only with issue), the query or script will be executed to return and fill the default value.
Usage could be :
We can currently only put a constant value inside.
I wonder if it could be possible to have instead a sql query inside for example or an empty ruby script generated systematically.
Each time a new issue is created (example only with issue), the query or script will be executed to return and fill the default value.
Usage could be :
- in a custom field for hours :
- fill the field with current hour or +x hours depending on the priority of the issue. But in this case, during creation of a new issue, each time a field is modified, custom fields must be calculated again ? unless they have been manually modified.
- it could be possible to create incremental id of trackers
I think possibilities will be huge and many existing trackers could be solved with this new feature.
The empty ruby script will be better because it will be necessary to have access to current project, user ...
The first aim is only to fill default value, this value will still be editable, but a read-only checkbox could be added eventually.
This is just a suggestion and I'm looking forward to have your feelings.
Updated by Go MAEDA over 7 years ago
- Subject changed from Default value of Custom fields to Dynamic default value for custom fields
Actions