A calculated custom field that represents the author of the last modification made to a field and is displayed as a String representing a username. It is a read-only field. |
To add a Last Field Value Change Author custom field to your instance:
Issues - > Custom fields.
Add custom field
.Advanced
in the left panel.Last Field Value Change Author Field
and select it.Next
.Create
Configure
and and specify the field to look for (explained below).If you have upgraded from JMCF |
Search template:
When creating a Last Field Value Change Author custom field, you can configure the Search template as User Picker & Group Searcher
to be able to search issues for a user in that custom field. If you select “None” for the searcher, then you won’t see any reference to this field in the Issue Navigator search fields. Note that changing a custom field searcher requires a re-index.
To specify the field to look for:
Configure
Edit Field to look for.
Field
drop-down.Save.
You can now define a velocity template that will return the Html representation of the calculated custom field. Leave it empty to use the default template.
To select a format for a Last Field Value Change Author custom field type value:
Configure
Edit Velocity Template
.Save.
You can use the following Velocity variables in the template:
$value
: the raw field value, an ApplicationUser
object.$formattedValue
: String representing a usernameFor example:
<font color="red"> $value </font> |
The Never show on Transition and Edit screens
option controls whether the calculated Single-user custom field can appear on transition and edit screens. If you select this option, the field will not be visible on any Edit or Transition screen, even if it is added to the screen.
You can access this field using any of the following getters of the Issue interface
get("Your custom field name") or get("customfield_xxxxx")
that returns a
ApplicationUser
getAsString("Your custom field name")
or
getAsString("customfield_xxxxx")
that returns a String
representing a username.