Page Comparison

Search template

When creating a Calculated Multi-user custom field type, you can configure the Search template as User Picker & Group Searcher to be able to search issues for users 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.

Configuring the Groovy formula for a Calculated Multi-user custom field type

To write a formula for the Calculated Multi-user custom field type;

1. Locate the custom field on the Custom Fields administration page.
2. Click on the cog wheel and click on Configure
3. Click on Edit Groovy Formula
4. In the editor write a Groovy script that returns a String representing a comma-separated list of usernames or an array of usernames or a collection of ApplicationUser objects. Also, you can test your script against any issue using the Groovy script tester.
5. Click on Save.

As documented on the Expected Value tab of the Groovy editor help, the Groovy formula must return either:

• A comma-separated list of usernames
• An array of usernames
• A Collection of ApplicationUser objects
• null or []

Examples of Groovy formula for a Calculated Multi-user custom field type:

• A Groovy expression returning a String representing the username

  Code Block
  language groovy linenumbers true
  "carter"

  
  

• A Groovy expression returning a String with comma separated values that represent usernames

  Code Block
  language groovy linenumbers true
  "carter,charlie"

  
  

• A Groovy expression returning an array of strings that represent the usernames

  Code Block
  language groovy linenumbers true
  ["carter","charlie"]

  
  

• A Groovy expression returning an ApplicationUser object

  Code Block
  language groovy linenumbers true
  issue.get("reporter")

  
  

• A Groovy expression returning a collection of ApplicationUser objects

  Code Block
  language groovy linenumbers true
  issue.get("Watchers")

  
  

Customizing the display of the Calculated Multi-user custom field type value on issue detail view

You can define a velocity template that will return the Html representation of the calculated custom field on the issue detail view. Leave it empty to use the default template. 

To write a velocity template for a Calculated Multi-user custom field type value:

1. Locate the custom field on the Custom Fields administration page.
2. Click on the cog wheel and click on Configure
3. Click on Edit Velocity Template.
4. Input the template.
5. Click on Save.

You can use the following Velocity variables in the template:

• $value: the raw field value, a collection of ApplicationUser objects.
• $formattedValue: String with comma separated values that represent the user display names, with avatars.
• and other variables described on this page

For example:

#set($separator = "")
#set($emailAddress ="")
#foreach($value in $value)
	#set($emailAddress=$emailAddress+$separator+$value.emailAddress)
	#set($separator = ",")
#end
$emailAddress

to display the Email Address of the users in the calculated field.

#if( $value.size() > 1 )
<span class="aui-lozenge aui-lozenge-success">$formattedValue</span>
#else
  <span class="aui-lozenge aui-lozenge-new">$formattedValue</span>
#end

displays the values in specific colored lozenge based on the number of users in the calculated field.

Customizing the display of the Calculated Multi-user custom field type value on search list view

You can define a velocity template that will return the Html representation of the calculated custom field in search result list views. Leave it empty to use the default template. 

To write a velocity template for a Calculated Multi-user custom field type value:

1. Locate the custom field on the Custom Fields administration page.
2. Click on the cog wheel and click on Configure
3. Click on Edit List View Velocity Template.
4. Input the template.
5. Click on Save.

You can use the following Velocity variables in the template:

• $value: the raw field value, a collection of ApplicationUser objects.
• $formattedValue: String with comma-separated values that represent the user display names, with avatars.
• and other variables described on this page

For example:

#set($separator = "")
#set($emailAddress ="")
#foreach($value in $value)
	#set($emailAddress=$emailAddress+$separator+$value.emailAddress)
	#set($separator = ",")
#end
$emailAddress

to display the Email Address of the users in the calculated field.

#if( $value.size() > 1 )
<span class="aui-lozenge aui-lozenge-success">$formattedValue</span>
#else
  <span class="aui-lozenge aui-lozenge-new">$formattedValue</span>
#end

displays the values in specific colored lozenge based on the number of users in the calculated field.

Displaying of the Calculated Multi-user custom field type on Transition and Edit screen

The Never show on Transition and Edit screens option controls whether the calculated Multi-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.

Accessing the Calculated Multi-user custom field from other Groovy scripts

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  Collection<ApplicationUser>

• getAsString("Your custom field name") or getAsString("customfield_xxxxx") that returns a String with comma separated usernames.