Page divider

Use the Page Break element to divide a long form into separate pages that submitters complete one step at a time, with Next and Back navigation.

How Page Breaks work

A Page Break acts as a divider in the form builder.

Everything above the first Page Break appears on Page 1. Everything between the first and second Page Break appears on Page 2, and so on.

Page numbers are calculated automatically based on the number and position of Page Break elements.

Add a Page Break

1. Open Smart Forms for Jira.

2. Create a new form or open an existing form.

3. In the form builder, find the Page Break element.

   

4. Drag the Page Break to the position where the next page should begin.

5. Add more Page Breaks when additional pages are needed.

6. Save the form.

The Page Break is displayed in the builder as a divider between pages.

Reorder pages

To change where a page starts, drag the Page Break to a new position in the form.

Page numbers are recalculated automatically after the Page Break is moved. The fields below the Page Break become part of the corresponding new page.

Delete a Page Break

To remove a page division:

1. Select the Page Break in the form builder.

2. Click Delete.

3. Confirm the action in the confirmation window.

Deleting a Page Break removes only the divider. It does not delete the fields placed below it.

The fields from the removed page are moved to the previous page.

Copy a Page Break

You can copy a Page Break in the same way as other form elements.

Only the divider is copied. The fields located below the original Page Break are not duplicated.

After the copied Page Break is added, page numbers are recalculated automatically.

Empty pages

An empty page can be created when two Page Breaks are placed next to each other or when all fields between them are moved or deleted.

Empty pages:

• remain visible in the form builder;

• are not shown to people filling out the form;

• are not included in the visible page count.

For example, if the builder contains three pages but Page 2 has no visible fields, form fillers will move directly from the first visible page to the next page containing fields.

Complete a multi-page form

Page navigation is available both for externally shared forms and forms opened inside Jira work items.

The buttons shown at the bottom of the form depend on the current page:

• First page: Next

  

• Middle pages: Back and Next

• Last page: Back and Submit

  

The progress indicator shows how far the user has moved through the currently available form pages.

The Next and Submit buttons use the configured form button color. The Back button uses a more subtle visual style.

Validation on each page

Validation runs whenever the user clicks Next.

Users cannot continue to the next page until all visible required fields and validation requirements on the current page are satisfied.

Validation runs again when the user clicks Submit on the final page.

This applies to:

• required fields;

• minimum and maximum character limits;

• numeric limits;

• minimum and maximum selection limits;

• regular expression validation;

• required fields displayed through Form Logic.

If a required field is hidden by Form Logic and is not part of the current user path, it does not block navigation.

Use Page Breaks with Form Logic

Page Breaks organize the form into pages, while Form Logic controls which fields are shown or hidden.

Pages follow a linear order. Page Breaks themselves cannot currently be used as When or Then elements in Form Logic.

Page groups in Form Logic

When selecting fields in Form Logic, form elements are grouped by page.

For example:

Page 1
  Request type
  Requester email

Page 2
  Hardware details
  Delivery location

Page 3
  Software details
  License type

This makes it easier to understand where each field appears in a multi-page form.

Selecting a Then element

When creating a new rule, the Then element can be selected only from:

• the same page as the When element; or

• a page that comes after it.

Fields from previous pages are not available for selection.

For example, when the When field is located on Page 2, the Then field can be selected from Page 2, Page 3, or any later page. Fields from Page 1 are not shown.

This helps prevent a form rule from revealing a field on a page the user has already completed.

Moving fields used in existing rules

Moving a field to another page does not automatically change or remove existing Form Logic rules.

For example:

1. A rule uses a When field on Page 2.

2. Its Then field is initially on Page 3.

3. The Then field is moved to Page 1.

The existing rule remains active, and no warning is displayed.

Review Form Logic after reorganizing pages to make sure every rule still supports the intended form flow.

Dynamic page flow

Form Logic can change which fields and pages are relevant to a particular user.

Pages that contain no visible fields for the current user are skipped automatically and are not included in the visible page count.

For example:

• Page 1 contains a Request type dropdown.

• Selecting Hardware shows fields located on Page 2.

• Selecting Software shows fields located on Page 3.

When Hardware is selected, the hardware page appears as the next page.

When Software is selected and Page 2 has no visible fields, the original Page 3 becomes the second visible page in the user’s form flow.

The page numbering and progress indicator update automatically based on the pages that are relevant to the user.

Page Breaks in submitted responses

Page Breaks help preserve the form structure after responses are submitted.

They are visible in:

• the Summary view in the Responses tab;

• the Individual response view;

• PDF exports.

Page Breaks are displayed as structural dividers, similar to how they appear in the form builder.

Page Breaks are not included in Excel exports because they do not contain response data.