-
Bug
-
Resolution: Fixed
-
Low
-
None
-
8.0.4
-
Severity 3 - Minor
-
0
Issue Summary
When you want to make the rule which includes the attachment name condition in A4J, you will check Jira automation conditions.
However, the smart value statement in that doc is not correct. This is documentation bug.
This is reproducible on Data Center: yes
Steps to Reproduce
- Step 1: Go https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html and check the "Issue attachments" section
filename {{attachment.filetype}}: the filename of the attachment
Expected Results
filename {{attachment.filename}}: the filename of the attachment
or
filename {{attachment.fileName}}: the filename of the attachment
Actual Results
filename {{attachment.filetype}}: the filename of the attachment
It doesn't work in rule.
Workaround
Please use the following correct smart value statement.
{{attachment.fileName}}
[JIRAAUTOSERVER-548] [Documentation] the smart value statement in the document is not correct
| Assignee | Original: Mateusz Ostaszewski [ mostaszewski@atlassian.com ] | New: Anna Przybycień [ 5b2ccddb8927 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| UIS | New: 0 |
| Labels | New: iq-a4j |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Priority | Original: High [ 2 ] | New: Low [ 4 ] |
| Summary | Original: [Documentation] Smart Value in Issue attachments doc is not correct. | New: [Documentation] the smart value statement in the document is not correct |
| Description |
Original:
h3. Issue Summary
When you want to make the rule which includes the attachment name condition in A4J, you will check [Jira automation conditions|https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html]. However, the smart value statement in that doc is not correct. This is documentation bug. This is reproducible on Data Center: yes h3. Steps to Reproduce # Step 1: Go https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html and check the "Issue attachments" section {code} filename {{attachment.filetype}}: the filename of the attachment {code} h3. Expected Results {code} filename {{attachment.filename}}: the filename of the attachment {code} or {code} filename {{attachment.fileName}}: the filename of the attachment {code} h3. Actual Results {code} filename {{attachment.filetype}}: the filename of the attachment {code} It doesn't work in rule. h3. Workaround Please use the following correct smart value statement. {code} {{attachment.fileName}} {code} |
New:
h3. Issue Summary
When you want to make the rule which includes the attachment name condition in A4J, you will check [Jira automation conditions|https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html]. However, the smart value statement in that doc is not correct. This is documentation bug. This is reproducible on Data Center: yes h3. Steps to Reproduce # Step 1: Go https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html and check the "Issue attachments" section {code} filename {{attachment.filetype}}: the filename of the attachment {code} !a4j-doc-smart-value-attachment-filename.png|thumbnail! h3. Expected Results {code} filename {{attachment.filename}}: the filename of the attachment {code} or {code} filename {{attachment.fileName}}: the filename of the attachment {code} h3. Actual Results {code} filename {{attachment.filetype}}: the filename of the attachment {code} It doesn't work in rule. h3. Workaround Please use the following correct smart value statement. {code} {{attachment.fileName}} {code} |