•  
      request #30389 Target field dependency is no longer auto-selected
    Infos
    #30389
    Joris MASSON (jmasson)
    2023-01-31 19:04
    2023-01-23 10:42
    31983
    Details
    Target field dependency is no longer auto-selected

    Given a tracker with field dependencies defined between selectbox / multi-selectbox fields, and given list-picker is not disabled with a feature flag for this tracker, when I create or edit an artifact of that tracker and I select a "source" value, then the "target" value will no longer be automatically selected. I must click to open the target field and click again to choose a value.

    When there is only one possible value (as configured in field dependencies), then it should be selected when I select the corresponding "source" value. This saves me two clicks.

    This was introduced by git #tuleap/stable/a4aa0b4475ef5ddb6cd95d689c3252db4cedf94b. list-picker used to select the first available value by itself, but this behaviour is desired only in tracker field dependencies context. It causes problems everywhere else. Thus, it was removed. We should instead edit the "field dependencies" javascript code itself so that it auto-selects target values.

    The target value is not selected despite being the only one possible

    Trackers
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Joris MASSON (jmasson)
    Closed
    2023-01-31
    Attachments
    The target value is not selected despite being the only one possible
    References

    Follow-ups

    User avatar
    Joris MASSON (jmasson)2023-01-23 10:42
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes