Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I need repeatable/dynamic rows on the portal? Please suggest

Rahul Borade
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 1, 2026

Anyone using Jira Service Management: I need a way on the customer portal form to let users add multiple expense line items (Type, Date, Amount, Description) with an ‘Add another’ button, instead of hard-coding Expense 1, 2, 3. Any Marketplace app that supports repeatable/dynamic rows on the portal? Name and quick feedback please.

2 answers

2 votes
Marc -Devoteam-
Community Champion
March 2, 2026

Hi @Rahul Borade 

@Shashank Dubey and @Arkadiusz Wroblewski are right.

Another option is to use a JSM form, but add sections and use a radio button field for a new set of options, make sure the to store the information in the field only.

Off-course you could use custom field and link them on the form filed, but in my opinion this is overhead, on storing this infromaiton.

 

2 votes
Arkadiusz Wroblewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 1, 2026

Hello @Rahul Borade 

Jira Cloud JSM doesn’t do “repeatable rows / add another line item” natively on portal forms. The form/table bits are basically static, so you end up with the ugly “Expense 1 / 2 / 3” pattern if you stay out-of-the-box.

If you want real line items (Type / Date / Amount / Description with an “add row” feel), the marketplace app I see used most for this is Table Grid Next Generation (iDalko). It gives you a proper grid/table field in Jira and you can expose it on the portal, so users can enter multiple rows without hardcoding fields.

Quick feedback: it’s the closest thing to “dynamic rows” in Jira, and it’s a common solution for expenses / order lines / inventory-style data. The tradeoff is: you’re adopting an app field type, so treat it like a platform decision (permissions, export/reporting needs, etc.).

Have a great Day ☀️🤠

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events