Versions Compared

Old Version 3

changes.mady.by.user Elena Kolesnik

Saved on

compared with

New Version Current

changes.mady.by.user Jonathan Muse

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Warning

Looking for the documentation on the newest versions of SIL Engine and the Simple Issue Language for Jira 8 for Server/Data Center? Click here !


Warning

The availability of the users personal data may be impacted by the recent changes by Atlassian in order to meet GDPR compliance. See the following for more information:


Info
titleAvailability

This routine is available starting with katl-commons 4.0.4.

This routine is available for Jira server and cloud deployment options.

Syntax

getFieldChanges(key, history_field_name)

...

Excerpt

Returns a list of tuples containing user|changeDate|field|oldVal|newVal for the selected field from the selected issue's history. Updated in v 4.8.0.8 to include two new fields - oldValString & newValString.

Parameters

Parameter name

Type

Required

Description

issue key

String

Yes

the key

Key of the selected issue.

field name

String

Yes

the name

Name of the selected field.

Return type

JFieldChanges JFieldChange []

The return value is an array of JFieldChange. The strings come in pairs; the . The first value is a date representing the time when the value was modified and the second value is the content of the requested field at that date.

...

Done. Program returned: admin|2017-05-23 13:28:09|Text Field|aaaaa|nnnnn

Notes

Note
  1. Beside Besides the labels/ids of the custom fields, also the name of the standard JIRA Jira fields (summary, assignee etc.) can be used as parameters.
  2. If it returns an empty array, you must get the last value of the field from the issue.
  3. The second parameter is the field name as it appears in history.

...