Each line of the custom field value should be in the format dimension1_key.,dimensionN_key,numeric_value (for example, ,john.smith,123 for the previous dimension names list example). Specify the list of dimension names that each line will return (for example, ). See the numeric measure with multiple dates example.Įnable custom measure import with numeric values for several dimension combinations. The custom field should return multiple lines where each line is in the format YYYY-MM-DD,numeric_value. See Jira custom fields for more information about numeric and date custom fields import as measures.Įnable custom measure import with numeric values for several dates. Please enable only for integer, decimal, date, or datetime data types. Increase the string datatype limit if needed.Įnable custom field import as a measure. See the Advanced settings for custom fields example above as well as the Scripted field example. See also the none_member_all_levels setting. If the custom field value is a concatenated string, then specify split_by that should be used to split a string into an array of strings. The custom field value should be an array with values for each level. If the custom field should be imported as a multi-level dimension then specify an array with level names (for example, ). This parameter json_fields works on eazyBI for Jira Cloud. If you create a new JavaScript calculated custom field, then specify the JavaScript code in this setting. If the custom field returns a time interval value, then specify the default time unit for the intervals range (for example, if "days" is specified then intervals with the value "/10" means that time intervals for every 10 days should be created). If you want to import ranges of numeric values as an interval dimension, then specify the default intervals (for example, "/10"). If the changelog string value is available for this custom field then enable import of this string value in eazyBI. In these cases quite often custom fields also provide string representation which is stored in the issue changelog (check Jira if you see the string values in the issue history when you change this custom field value). Some custom fields return numeric ID values as their default values, but you would like to import the corresponding string display value in eazyBI. This setting is supported only for data type string, integer, or decimal. Enable only for list-of-values custom field types and not for custom fields that have unique values for each issue. Use date for date values without the time and datetime for dates with time.Įnable custom field import as a dimension. Specify precision (default 15) and scale (default 2) for decimals, if you want to change the defaults. Use integer and decimal for numeric values. Use string for limited length strings (the default limit is 255) or text for large text properties (do not use text when enabling dimension). Specify the data type of the custom field value and that should be stored in eazyBI. You can use this additional CSV dimension if you want to filter measure values for issues that have both values in the custom field. If csv_dimension is enabled, then in the Custom field CSV dimension one member with comma-separated values ( one, two) will be created and the corresponding measure values will be stored for this member. If enabled then additional Custom field CSV dimension will be created where used combinations of values (as comma-separated string) will be imported.įor example, if an issue has a custom field with values one and two, then in the multiple values dimension Custom field two separate members ( one and two) will be created and the corresponding measure values for this issue will be stored for each of these members. This report uses the same Confluence page for demonstration as per CONF-14185.This parameter check_calculated_value does not work for calculated JavaScript custom fieldsĬan be used with custom fields that have dimension and multiple_values enabled. block.Įxample page on EAC: Noformat square brackets in title escape testĮxample page on CAC: Noformat square brackets in title escape test To be removed in a future version of Confluence.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |