nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Fields, tabs according to conmponent chosen

Rumceisz

Hi All,

we would like to configure a project where we could define the to be filled fields according tho the component chosen. Specifically this a sys admin project where the users could raise incident and requests. When submitting request they have to first choose the type: e.g. firewall change, SVN access, etc. and based on this type they should have to fill different fields.

We know about cascading field but we need more fields and more difficult achievement. So cascading does not meet our requirements. And using different issue types for each type is also not very good.

Could you please give us some hints?

Thanks in advance,

Rumi

Accepted answers

Jobin Kuruvilla [Adaptavist]

You might be able to take advantage of the workflows if you are okay with entering the rest of the details after creation.

Enter only the basic details on Create and then have different transitions based on components to capture the rest of the fields. The fields will be captured in the transition screen. Not the best way to do but easier than customizations if you can't go for different issuetypes.

All comments

Peter Van de Voorde

Hi Rumceisz,

Wouldn't it be easier to do this by creating several issue types (Firewall change request, svn access request,...) and use different screen schemes for each issue type?

That's how I would do it.

I don't know of a way to do it based on components (what are you going to do if they add 2 or more components?)

Best regards,

Peter

Nic Brough -Adaptavist-

To echo what Peter says, there's no way to do this based on component (plus, components are multi-select, which doesn't really fit your model).

You really should do this with issue types, and fields/configurations tied to the issue type. It's definitely the model that fits your need.

Jobin Kuruvilla [Adaptavist]

You might be able to take advantage of the workflows if you are okay with entering the rest of the details after creation.

Peter Van de Voorde

Hey Jobin,

How would it handle multiple components? Will it give multiple transition possibilities?

Best regards,

Peter

Jobin Kuruvilla [Adaptavist]

Multiple components will open up multiple transitions. Honestly, that is something they will have to consider in the design. If they have fields per components, I hope they have considered the multiple components scenario

Maybe they should scrap components and go for a select list field instead and do the same thing if multiple components are not an option.

Nic Brough -Adaptavist-

Depends on how you phrase the conditions.

Let's say you've got components A, B and C. You create one transition per component, and put conditions on them so that "Transition for A only appears if A is selected in the component field". It'll be fine when your users choose only one component, but if they select components A and C, then they'll be offered transitions for A and C. That's a bit of a nightmare, because if they choose A, they won't be offered fields that related to C.

You could change that to "Transition for A only appears when they have A *and only A* on the component field", but then you need to deal with the situation when more than one component is there. For that, you'd need a catch-all, which offers ALL the fields etc for every component.

Or, don't use components, use another, single-select field. Which might as well be issue type ;-)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration