Use result from Jira query to create smart dropdown or smart radio group

[JiraAdmin]

Objective:

In a Confiforms form, for a selected Jira Project, obtain a list of active Epics. Allow the user to select one of the Epics. The selection will be used to obtain additional information regarding the work being done in that Epic.

Details:

• Using Jira and Confluence Data Center.
• There is a Jira Project for each geographic area of the world. For example, North America, South America, Europe, Asia, Africa, Pacific. The list of Project keys is maintained in a separate form. Using a Smart Radio group, the user selects the region for which they want information.
  • Selection is limited to a single geographic region (Jira Project), thus the Smart Radio group.
• The Epic issue type represents a project that is active in that region.
  • For example, Obsolete Hardware Replacement.
• Using a helper Confiforms form, a query is executed to return the key and summary for each active Epic in that region. 
  • JQL: project = NAM AND issuetype = Epic AND status NOT IN (Done, Cancelled)
  • API Parameters: &fields=key,summary
• From the query result, the user selects the Epic for which information is needed.

Current Status:

• Project selection works.
• The helper form returns the list of Epics in JSON format.
  • Using the IFFT Applink Service.
• The helper form returns the result to a field in the main form.

Question:

• Is it possible to convert the query result to a Smart Radio group so the user can select a single Epic from the list?

Do you have any questions? Do you have any suggestions or is there a better way to achieve the same result?

Thank you.

[Stéphane Veraart]

In theory this is possible using API calls to update the custom field options. Yet the important question is: what do you want to do with the existing values? The best option would be to disable the value to maintain the previously entered data as it was.

To be able to convert the JSON into a list that can be used in an API call you need to write code that runs outside of Jira doing the API calls or use scripts within Scriptrunner to make it happen.

[Stéphane Veraart]

One addition to the previous point is that you need to know what values are already there, not to create duplicate values. This would require more complex coding/scripting to check which values are already there, which are still needed, which need to be disabled and which need to be added.