| 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 | ||
|---|---|---|
| ||
This routine is available starting with SIL Engine™ 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||field|oldVal|newVal for the selected field from the selected issue's history. |
...
Parameter name | Type | Required | Description |
|---|---|---|---|
issue key | String | Yes | The key Key of the selected issue. |
history_field _ name | String | Yes | The name Name of the selected field. |
Return type
JFieldChange JFieldChanges []
The return value is an array of JFieldChange. The strings come in pairs:
...
. 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.
Example
| Code Block |
|---|
JFieldChange[] changes = getFieldChanges("TEST-10", "My Text Field");
return changes; |
Result:
admin|2017-05-23 13:28:05|My Text Field||test|admin|2017-05-23 13:28:09|My Text Field|test|lalaa
...
| Code Block |
|---|
JFieldChange[] changes = getFieldChanges("TEST-10", "customfield_10200");
JFieldChange latestChange = changes[0];
date newest = latestChange.changeDate;
for (JFieldChange change in changes) {
if (change.changeDate > newest) {
latestChange = change;
}
}
return latestChange; |
...
Done. Program returned: admin|2017-05-23 13:28:09|Text Field|aaaaa|nnnnn
...
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|