-
Bug
-
Resolution: Unresolved
-
Medium
-
Severity 3 - Minor
-
0
Issue Summary
The field value changed trigger does not work in A4J (Automation for Jira) rule when you select the time tracking or log work fields
Steps to Reproduce
- Create an Automation Rule with issue trigger name: field-value changed
- Select the field "Log work" from the trigger drop down
- Add any action to the rule to save
Expected Results
Once we change the field value such as the Original estimate or log work on the issue, it should trigger the rule.
Actual Results
It doesn't trigger the rule.
Workaround
Please use the "Work logged" issue trigger.
[AUTO-382] The field value changed trigger does not work for some fields - time tracking, log work, attachments added via comments
UIS | Original: 1 | New: 0 |
Summary | Original: The field value changed trigger does not work for some fields - time tracking, log work, attachments | New: The field value changed trigger does not work for some fields - time tracking, log work, attachments added via comments |
Summary | Original: The field value changed trigger does not work for time tracking and log work fields | New: The field value changed trigger does not work for some fields - time tracking, log work, attachments |
Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
Labels | New: jsw-s13 |
Component/s | Original: Automation [ 68402 ] | |
Component/s | New: Trigger - Other [ 70304 ] | |
Key | Original: JSWCLOUD-22980 | New: AUTO-382 |
Support reference count | Original: 4 | |
Project | Original: Jira Software Cloud [ 18511 ] | New: Automation for Cloud [ 22610 ] |
Hi
I created a workaround for adding attachments in comments - https://community.atlassian.com/forums/Jira-questions/The-Field-value-changed-trigger-does-not-work-for-some-fields/qaq-p/2966826
Hope that will help some of you as a workaround but still I'm waiting for fixing this bug!