...
Asset imports can utilize dynamic date placeholders like {{jiraDate}} to automatically insert the current date into the import URL. This allows the import process to dynamically access files that are regularly updated with date-based filenames, ensuring that the most recent data is always imported. For example, using {{jiraDate}} will insert the date in a format like "2024-08-13", making it easier to target files with date-specific naming conventions. This feature enhances flexibility and automation in managing and importing date-sensitive assets.
...
Format
...
Thursday, November 1, 1979 6:23:12 AM UTC
...
Default (none specified)
...
1979-11-01T11:23:12.0+0000
...
jiraDate
...
1979-11-01
...
jiraDateTime
...
1979-11-01T06:23:12.0-0500
...
jqlDate
...
1979-11-01
...
jqlDateTime
...
1979-11-01 06:23
...
shortDate
...
11/1/79
...
shortTime
...
6:23 AM
...
shortDateTime
...
11/1/79 6:23 AM
...
mediumDate
...
Nov 1, 1979
...
mediumTime
...
6:23:12 AM
...
mediumDateTime
...
Nov 1, 1979 6:23:12 AM
...
longDate
...
November 1, 1979
...
longTime
...
6:23:12 AM EST
...
longDateTime
...
November 1, 1979, 6:23:12 AM UTC
...
fullDate
...
Thursday, November 1, 1979
...
fullTime
...
6:23:12 AM EST
...
fullDateTime
...
map a attribute to a Object Type in CSV import?
Enter the URL of the resource and click "Load." This will display the attributes and their corresponding types.
To map an attribute to an Object Type, select "Type" as "Reference Object" and fill in the two additional fields:
Ref. Obj. Type: Enter the name of the object type you want to reference. Ensure it is spelled correctly.
AQL Field: Provide the query for mapping the data. Use the format
"Attribute Name" = ${Number} "Name" = ${6}, where "Name" is the attribute in the referenced type, and${6}is the corresponding value. You can use more advanced queries as well if needed.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|