Multiple Entries for same fields in portal

[Ricardo_Gomes]

Hi,

A simplification of my use case would be as follows - 

As a portal user, I want to be able to create multiple entries of an object composed by 3 elements/fields (two dropdowns and one single user picker) selections using the same portal form.

Example:

[dropdown 1]

• option a
• option b
• option c

[dropdown 2] based on the option selected in dropdown 1, you would potentially see different options in dropdown 2

• option d
• option e
• option f

[dropdown 3 - single user picker] based on selection in dropdowns 1 and 2, 3 would allow a single user to be entered which would be associated with entry values from dropdowns 1 and 2.

Example: 

a > e > John Doe

So far so good... Now, what I'm trying to solve now is that the combination above can happen multiple times under this same context. So, potentially, my portal user would use this same process to enter multiple entries (preferably using the same fields without having to create multiple duplicate fields in the form) so the final result after those entries would be something like (as an example):

a > e > John Doe

b > d > Jane Doe

c > f > Mike Doe, 

and so on...

GOAL - 

My ultimate goal would be to create a subtask in the backend for each of the 3 combinations above.

QUESTION - 

Is there a way to accomplish this without any plugins just by using Forms in such a way that is more elegant to portal users?

Or the only way would be to pre-create multiple repeated sections on the form? I'm trying to avoid displaying multiple sections there that would look like this:

{SECTION 1 for combination 1}

• [dropdown 1]
• [dropdown 2]
• [user picker]

{SECTION 2 for combination 2}

• [dropdown 1]
• [dropdown 2]
• [user picker]

{SECTION 3 for combination 3}

• [dropdown 1]
• [dropdown 2]
• [user picker]

And so on...

This would be not only non-elegant but also kind of a dumb solution. Besides, I don't really know how many entries there could be for a single form interaction...

Thank you for your help!

[Mikael Sandberg · Accepted solution]

Yes, currently it is only possible to do with pre-created sections based on what was selected in the first dropdown.

If you are on the Premium plan or higher you could use Assets and then control what is available in dropdown 2 and user picker based on what is select in dropdown 1. Assets support filter issue scope to accomplish this.

I have a form for peripherals and based on what location is selected the peripheral field is only showing items for that location.

[Ricardo_Gomes]

Thanks @Mikael Sandberg .

It sounds like I would have to create multiple versions of the 2nd dropdown and hide the ones not being used based on the option selected by the user in the first dropdown.

Also, this is a multi-entry object so if I pre-define users will be able to enter up to 5 entries of that object, that means I'll have to create 5 dropdowns for the first option and 5 x 5 = 25 for the 2nd option so I can hide/show only the 2nd options that relate to the first option selected in the first dropdown.

Since I don't have JSM Premium and I can't read form field values yet (currently under development by Atlassian), I don't see any other alternative.

In the backend I would have to have an automation that would read all those options selected through all the 25+5 fields and then create the 5 subtasks for each pair of option selected by the user for all five entries.

Does this make sense to you?

This is a LOT of workaround for something so simple. 

Atlassian is also working on a cascading form field which would help me quite a bit, which is currently in progress here (FYI):

https://jira.atlassian.com/browse/JSDCLOUD-10792

The work to make form field values readable through smart values can be tracked here:

https://jira.atlassian.com/browse/JSDCLOUD-10697

Cheers!