Supported fields

A Customer Actions form can contain a set of Jira fields. You add them on the Design tab, as described in Create a form. This page lists the fields and shows how customers edit them in the dialog.

Fields a form can contain

How customers edit fields

Most fields use a control that matches their type, for example a text box for text and a drop-down for a list. These fields work differently:

• Description and Paragraph: a rich-text editor.
• Cascading select: a parent drop-down and, when the parent has children, a child drop-down. Customers can clear both.
• Labels: a multi-select with suggestions from Jira. Customers can type a new label.
• Date time picker: a calendar and a time list in 30-minute steps. Customers fill both the date and the time, or clear both.
• Assignee, Reporter, User pickers, and Request participants: a user picker. With Allow to browse users from Jira on, customers search users by typing, up to ten matches. With it off, they type a full email address. If you limited a user picker to Jira groups, the search finds only members of those groups.
• Comment: an empty text area. The text becomes a new comment, and customers can’t edit existing comments.

Rules in the dialog

• A field has a label above it: the name on the form of the request type, or else the name of the Jira field.
• A field is required, and has a red asterisk, when any of these is true:
  • the form of the request type requires it;
  • the Jira field configuration marks it as required;
  • the Required setting of the form is on.
• A field that isn’t on the edit screen of the request doesn’t appear in the dialog. If no object of the form can appear, the link of the form isn’t shown either. To find such problems, see Manage forms.
• Feature Bundle saves only the fields the customer changed.