How can I relate a couple of custom fields to each value of another field?

[Thomas Kemp]

I would like to have two numeric value custom fields  (changeable/editable) to be related to either:

   A. each entry of custom field Select List (multiple choices) or

   B. each entry of the version field.

For either way, how can I relate the two numeric custom fields?

In my scenario:

Each issue of the project is an errata. 

Each of the two numeric custom fields would be related severity values. 

The Select List or Version field holds the releases to which the errata apply.

Also, Is there another way to structure this scenario for better results?

[Nic Brough -Adaptavist-]

I'm afraid the requirement is not clear - you say you want to "relate" these two fields together, but I can't work out what that really means.  What does "each entry of custom field (multi) select" mean?  Yes, it's a multiselect.  Of what?  What impact does selecting A, 4 and zyz on there have on the other field?  What is "each entry of the version field"?  Are you wanting multiple selects of versions?  If so, what effect does that have on the other?  If I select versions 1, 3, and 9, what happens?

Without un-muddling that, all I can really do is tell you

1) Have a look at the cascading select field

2) Have a look at the "Behaviours" stuff in the script runner addon

[Thomas Kemp]

Hi Nic,

I'll try to be more clear.

Looking at my option A.  I would have a custom field created using a Select list (multiple choices) configuration.  When the issue is created or edited, the user can select multiple items in this custom field.  For each selection made, I would like two other fields created that are related (1 to 1 relationally related) to the selection.

Example:

  The issue is an errata against a product.  The issue has the select list as a field.  The user selects 2 choices from the select list.  These correspond to the widget 100 and widget 120 products, signifying that the issue (errata) applies to these two widget projects.  Once widget 100 is selected, I would like to have 2 fields created that relate to it.  These two custom fields could be named "Hardware impact" and "Software impact".  So, widget 100 could have a hardware impact of 3 and a software impact of 1.  Widget 120 could have a hardware impact of 0 and a software impact of 5.

Looking at my option B.  I would use versions for the widgets.  So, I would have an issue represent an errata.  In the version field, I could create version "widget 100" and version "widget 120".  For each version I would like to have two fields related, "Hardware impact" and "Software impact".  So, version "widget 120" could have a hardware impact of 3 and a software impact of 1.  Version "widget 120" could have a hardware impact of 0 and a software impact of 5.

Does this help identify what I'm trying to use the JIRA issue for and the fields?  Is there a better way?

I will look at the two suggestions.  With my (attempted) clarification, would one of these work for me?

Thanks!