Add support for variable-length (repeater) table fields in Jira Service Management request forms

XMLWordPrintable

    Current Problem:

    Currently, Jira Service Management request forms require administrators to predefine a fixed number of fields for each record when handling multiple entries in a single request. For example, in a user addition request, fields such as "Name," "Email," "Department," and "Permission details" must be prepared for each user in advance.
    However, the actual number of records (e.g., users to be added) varies with each request. This leads to the following issues:

    The form becomes excessively long and unwieldy as the number of records increases.

    It is not practical to prepare a fixed number of fields for every possible scenario.

    The user experience (UX) deteriorates, especially when many records are involved.

    The need for multiple columns (e.g., permission details) exacerbates form saturation.

    Both requesters and approvers would benefit from a more natural, table-like input method that allows for a variable number of records.

    Suggested Solution:

    Introduce a new field type for Jira Service Management request forms:
    A variable-length (repeater) table input field, similar to "Add Row" tables or "Repeater Fields" found in Confluence and other web form products.

    Key requirements:

    • Each record consists of a set of fields (e.g., Name + Email + Permission set).
    • Users can dynamically add or remove rows (records) on the form via an "Add Row" button or similar UI.
    • The submitted data can be stored as a single field in JSON or CSV format (encoding is flexible).
    • The field should be compatible with Jira Automation and API for post-processing.
    • The feature should be generic and not limited to specific use cases (e.g., user addition).

    Workaround:

    Currently, administrators must create a fixed number of field sets in advance, which is not scalable or user-friendly. Alternatively, users may be instructed to upload CSV/Excel files, but this is less integrated and complicates automation and downstream processing.

    Expected Benefits:

    • Significantly simplifies complex request UIs.
    • Reduces the burden on users submitting requests.
    • Enhances the flexibility and extensibility of Jira Service Management.
    • Facilitates smoother migration from other systems that use CSV/Excel-based workflows.

    Reference:
    This feature is similar to "Add Row" tables or "Repeater Fields" available in Confluence and other web form solutions.

            Assignee:
            Unassigned
            Reporter:
            Jun Itokawa
            Votes:
            6 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: