getredash/redash

JQL cannot return child custom field value

Open

#3340 opened on Jan 25, 2019

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Python (24,845 stars) (4,236 forks)batch import
BackendBughelp wanted

Description

Issue Summary

Cannot display JQL result with customfield type like radiobutton, list single, list multiple, ...

Steps to Reproduce

  1. Create a customfield in JIRA like "Select List (cascading)". Setup the field behaviour "options" with values.
  2. Create Jira issue and choose the value in list.
  3. Create in redash a new jql query like:
{
    "fields": "summary,priority,customfield_xxxx",
    "jql": "project = \"xxxx Service Desk\""
}

The column appears in the result set but there is no value.

For example, here is what I get with postman with a get on : https://myhost/rest/api/2/search?jql=issuekey=LSD-31401

"customfield_13592": {
"self": "https://myhost/rest/api/2/customFieldOption/14340",
"value": "Software",
"id": "14340",
"child": {
"self": "https://myhost/rest/api/2/customFieldOption/14372",
"value": "MySoftwareValueChild",
"id": "14372"
}

As you can see the customfield value is “MySoftwareValueChild”.

To search for this kind of value in jira, I use jql cascadeOption() function , first value is the parent and second value is the child value. See https://confluence.atlassian.com/jiracoreserver073/advanced-searching-functions-reference-861257222.html#AdvancedSearchingFunctions-cascadeOption%28

Technical details:

  • Redash Version: 6.0.0
  • Browser/OS: Firefox
  • How did you install Redash: docker-compose (dev)

Contributor guide

Tech stack
pythonsqlrest api
Domain
backendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
familiarity with Jira custom fieldsunderstanding of Redash's JQL implementation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the JQL data source in Redash, likely in the file `redash/query runner/jql.py` (or similar). The issue is that Redash's JQL query runner does not recursively extract child custom field values from the JIRA API response. Look at how the custom fields are parsed and ensure that nested 'child' object is flattened into a string. Check comments in the issue for any additional context. Consider testing with a cascading select custom field.