Page tree
Skip to end of metadata
Go to start of metadata

What is it?

This custom field is not an editable field but it allows you to identify dynamically one or more users following different rules. The goal is to identify users from another User Field from an Issue (same issue or not, from same project or not) identified by different ways.

How to configure ... ?

For adding this new Custom Field ... 

  1. Select and Add the Custom Field Type Multi Users from other User Customfield 
  2. Then go to Configure.
    You will have a set of Configuration Items allowing to complete the expected configuration ...

    • Issue Identification Modes.
      It will allow to specify which modes will be used to identify the Issues.

    • Issue Fields.
      Which Fields to use to identify Issue.

    • Linked Issue Type
      Which Issue Type will be considered from Linked Issue

    • Link Issue Type
      Which Link Issue Type will be considered from Linked Issue
    • User Fields
      For identified Issues, which Users Fields will have to be considered to built the final list of Users.

    • Display Mode
      And finally, which rules will be followed to render Users.

    Configuration Items

  3. Start to specify which Issue Identification Modes have to be used.

    You will be able to combine 4 different modes, that will allow you to identify an Issue or a set of Issues.

    Options are :

    • Current Issue 
    • Issue(s) identified by Issue Field
      It means any Custom Field in Current Issue where the value is an Issue Key or Issue Id.
    • Issue(s) identified by Issue Type
      Among all Issues currently linked to the current Issue, the ones that match with specified Issue Type will be considered.
    • Issue(s) identified by Link Type
      Among all Issues currently linked to the current Issue, the ones, where the Link Issue Type matches the specified Link Issue Type, will be also considered.

    Issue Identication Modes

    After having selected which modes will be retained, the others will be marked as disabled as follow ...
    Disabled Issue Identication ModesIf there are enabled, then you will have to complete their configurations ...

    1. In case of Current Issue mode ...
      Nothing special to configure.
    2. In case of Issue Field mode ...

      You will be able to select one of more Issue Fields. They will be used to identify considered Issue.

      They can be any of available type of field. Their value will be evaluated as Issue Key or Issue Id.

      Configuration of Issue Fields

    3. In case of Linked Issue Type mode ...

      You will be able to select the Issue Type to consider for identifying the considered Issues

    4. In case of Link Issue Type mode ...

      You will be able to select which Link Issue Types to consider for identifying the considered Issues.

      The available Link Issue Types will be proposed in 2 separate lists :

      • Outward Link Issue Types
      • Inward Link Issue Types

      Configuration Link Issue Type

  4. When you have defined how considered Issue(s) will identified, in next step, you will define where to pick Users ...

    You will be able to select one or many User Fields among any System or Custom Field as soon as they return a User or set of User.

    This Returned Type is tested by introspection in among all available Custom Fields. Following Java Type will be considered:

    • User
    • ApplicationUser
    • Collection<User>, then also List<User> and Set<User>
    • Collection<ApplicationUser>, then also List<ApplicationUser> and Set<ApplicationUser>

    Configuration Users Fields

  5. And, finally, it will remain to specify Rendering Rules ...

    For this Custom Field, the Rendering Rules means to specify :

    • How the list of found Users will be rendered ?
      Only the option Users is available.
      (instead of Single and Multi Project Role Pickers)

    • If the Assignee fields required to be hidden ?
      I may have a sense if the currently Custom Field will be likened to an Assignee field.

    • If the current Field has to be displayed if it is empty ?
      When no User is found, it may have a sense to display the field is empty.
      (like Unassigned for Assignee field).

    Configuration Display Mode

Your Custom Field is now configured ...

Field Configured

At this stage, your Custom Field is configured ...

In the sample configuration on left ...

  • We will consider all Issue Identification modes ...

  • Considered Issues will be :
    • The Current Issue,
    • Any Issue identified by the field Related Issue (here a simple Text),
    • All Story Issues that will have a link with the current Issue
    • Due to the inward and outward links, the Parent Issue of current Issue (if it is a Sub-Task) or all Sub-Tasks of Current Issue (if it is a Standard Issue)

  • From all of these considered Issues, your new Custom Field will aggregate all Users identified in below User Fields :
    • Assignee,
    • Reporter,
    • Multi User from other User.

      tinymce.emotions_dlg.warning Note that your Field will be not considered in the Current Issue, to avoid infinite circle tinymce.emotions_dlg.warning

  • And finally, found users will be simply displayed, without hiding Assignee field, and only if at least one users is found.

You will be able to use this field in :

  • Permission Schemes
  • Issue Security Levels
  • Notification Scheme

I let you evaluate the numerous possibilities !

Some usage cases to share ...

Below, it will be a pleasure to list your best usages of this Custom Field ... The simplest to the more complex.

Do not hesitate to share them or raise encountered limits in your tries ! 

On this page:

Useful hint

See also ...

  • No labels