A Status entered by user custom field type represents a user who last (or first) moved the issue to the specified status and is displayed as a String representing the user display name. It is a read-only field. |
To add a Status entered by User custom field type to your instance:
Issues - > Custom fields.
Add custom field
.Advanced
in the left panel.Status entered by user custom Field type
and select it.Next
.Create
Configure
and specify the status(es) and the order of status entered (explained below).Search template
When creating a Status Entered by User custom field type, 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 status(es) to look for:
Configure
Edit Status(es).
Save.
You can also configure the custom field to look for the current status. |
To specify the order of the selected status(es) that the field should look for;
Configure.
Latest
or Earliest
from the Status order
field to capture the last or first status entered order respectively.You can 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 the Status entered by user custom field type value;
Configure
Edit Velocity Template
.Save.
You can use the following Velocity variables in the template:
$value
: the raw field value, the ApplicationUser object.$formattedValue
: a String representing the display name of the userFor example:
<div style="border: dashed"> $formattedValue </div> |
displays the formatted value of the field with a dashed border.
Now you can control the display of the Status entered by user custom field on the transition and edit screens. If you select this option, the field will not be visible on the Edit and Transition screens, even if added to them.
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.