Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-382

Changelog to trigger the last issue changes without needing to specify the custom fields with smart values

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Smart-values
    • 0

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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}}
/

          Form Name

            [JIRAAUTOSERVER-382] Changelog to trigger the last issue changes without needing to specify the custom fields with smart values

            No work has yet been logged on this issue.

              Unassigned Unassigned
              6bebacf0c7e4 Aline Staudt
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: