-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Description
Currently, the changelog is limited to certain custom fields that need to be referenced in the rule.
{#changelog.summary}} {{toString}} {{/}} {{#changelog.issuetype}} {{fromString}} {{/}} // Previous status name {{#changelog.status}}{{fromString}}{{/}} // Previous status id (for using in another Edit action {{#changelog.status}}{{from}}{{/}}
Suggestion
Create a changelog trigger that will gather the last changes made in an issue, without needing to specify which fields should show up the changes, in order to trigger the entire changes performed lastly in an issue.
Example:
#changelog field was updated from {{fromString}} to {{toString}} /
- relates to
-
JIRAAUTOSERVER-39 Provide a smart value to get the name of transition
- Future Consideration
-
A4J-2920 You do not have permission to view this issue
- links to
[JIRAAUTOSERVER-382] Changelog to trigger the last issue changes without needing to specify the custom fields with smart values
Labels | Original: iq-a4j | New: iq-a4j ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979136 ] |
Link |
Original:
This issue relates to |
Remote Link | Original: This issue links to "A4J-2920 (Bulldog)" [ 608691 ] | New: This issue links to "A4J-2920 (JIRA Server (Bulldog))" [ 608691 ] |
UIS | New: 0 |
Labels | New: iq-a4j |
Remote Link | New: This issue links to "A4J-2920 (Bulldog)" [ 608691 ] |
Link |
New:
This issue relates to |
Link | New: This issue relates to JIRAAUTOSERVER-39 [ JIRAAUTOSERVER-39 ] |