Allowing user to Populate multiple values in one EPIC

[Munir Patel]

Is there any way for a user to populate multiple values in an EPIC

SKU#s

Flavour  

example would be:

Sku1, Vanilla

Sku2, Orange

Sku3, Mango

[Nic Brough -Adaptavist-]

If I understand this correctly, you are trying to have a "field" which can have many lines, but each line is entered separately, like adding rows to a table.

Jira does not have fields that do that.  You say you need up to 20 lines, so the closest you can get is adding 20 fields, and leaving the ones you don't need empty.

[Munir Patel]

you have a correct understanding. Need a two dimensional table that can populate SKUs and their associated flavour

[Nicolas Tagle]

Hi Munir,

The field you are looking for is a cascade option select. That will allow for the selection of SKU and then Flavor associated. Let me know if you have any question on how to create such field.

Best regards,

Nico.

[Munir Patel]

Hi Nocolas,

SKU field is not a dropdown. Can a user enter any value.

[Trudy Claspill]

You can create custom field(s) to support entry of values, and associated the custom fields with just the Epic issue type and the screens used for the Epic issue type.

Are you working with a Team Managed project or a Company Managed project?

https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/

https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/

[Munir Patel]

Company Managed Project. 

I am not clear about your solution. can you please elaborate with example

Thanks for response

[Trudy Claspill]

Hello @Munir Patel 

You will need to provide more information in order for me to provide more detailed guidance.

Are you working with a Software, Service, or Business project? That will be specified at the top of the navigation pane on the left below the project name.

Do you want SKU1, SKU2, and SKU3 to be separate fields, each holding a value? Or is there just one field in which the user can select/enter the values "Sku1, Vanilla", "Sku2, Orange", "Sku3, Mango"?

Do you want to allow the user to enter any text, or select from a list of supplied values for each field?

[Munir Patel]

Hi Trudy,

working with software project.

SKU1, SKU2, SKU3... be in one field as I don't want to create several fields. It can go upto 20s.

Would like to provide user one field to enter SKUNumber(s) [not from the dropdown] and associate it with flavour.

Example:

Field1          Field2

SKU00001    Vanilla

SKU00005     Orange

...

...

SKU00011     Mango

Field 1 is not a dropdown

Field 2 can be a dropdown or whatever

[Trudy Claspill]

Hello @Munir Patel 

Then you will need to create two Custom Fields.

For a Company Managed project, this is the document that provides an overview of creating custom fields.

https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/

That document includes a link to another document that details the types of custom fields available.

https://support.atlassian.com/jira-cloud-administration/docs/custom-fields-types-in-company-managed-projects/

For the SKU entry field you would need to create a "Short Text" field.

For the Flavor field, if you want it to be a pick list of values that you supply, restricting the users to select only what you make available, then that field would need to be a Select List (Single Choice) field.

When you create a custom field the wizard automatically next displays a list of screen to which you can add the field. You will need to know the screens associated with the Epic issue type in the destination project(s), and check the boxes to add the fields to those screens.

If you are using the same screens for Epic and other issue types, and you want these fields only on the Epics, then you will need to create new screens to be used only be the Epic issues, create a Screen Scheme for the Epic issue type, and add that Screen Scheme to the Issue Type Screen Scheme associated with your project(s).

There are tutorial videos available on YouTube.

https://www.youtube.com/watch?v=sO_kaGzcJ8Y

https://www.youtube.com/watch?v=INBf1EVknd8

There are other videos available which you can find if you search.

[Munir Patel]

How will I link the two custom fields

SKU1 linked to flavour vanila

SKU2 linked to flavour orange

[Trudy Claspill]

I think we need more information about your use case.

1. Does a single issue get more than one value for SKU?

2. Does a given value for SKU have one and only one associated flavour?

In my guidance I was assuming:

A. Only one SKU value is entered per Jira issue.

B. The SKU value entered did not affect what Flavour could be selected.

With those assumptions there is no "link" inherent between the fields.  They simply represent two pieces of information related to your Jira issue.

Can you provide one or more example detailed scenarios for how this data would actually be used with a Jira issue?

[Munir Patel]

Under a single Issue which in real life represents an Idea for innovation of a product. In Jira it would be an EPIC. Under this EPIC there will be a combinations of different versions of products called SKUs and each SKU will have a flavour associated to it.

If under an EPIC there are say 4 versions of SKU identified then it should look like below.

SKU1 with say Vanila flavour

SKU2 with say Chocolate flavour

SKU3 with say Orange flavour.

There will be multiple SKUs [versions] each one of which will be associated to one flavour

something like a two dimensional table

[Trudy Claspill]

In that case see @Nic Brough -Adaptavist- 's answer. 

[Munir Patel]

Thanks Trudy, appreciate all your time and efforts and responses.