Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #11397 Shared Field doesn't follow change of source field
    Actions
    Infos
    #11397
    Mathieu Auvray (auvraym)
    2021-01-05 13:34
    2018-04-12 22:18
    11715
    Details
    Shared Field doesn't follow change of source field
    Use case :
    Step 1 : I define a Select Box in a Tracker 1
    Step 2 : I Create a Shared field on tracker 2, field ID is the one of SB define in step 1
    Step 3 : I change the Select Box in a Multi Select Box in tracker 1

    Result : The shared field in tracker 2 is still a SB and not a MSB
    Trackers
    9.19
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Yannis ROSSETTO (rossettoy)
    Closed
    2021-01-05
    Attachments
    Artifact links
    Empty
    Empty
    References
    Referencing request #11397

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/00/21200/4' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 77427c9ac1
    User avatar Lorentz Romain (lorentzr) , 2021-01-05 13:32
    request #11397 Shared Field doesn't follow change of source field 24fca5bab5
    User avatar Yannis ROSSETTO (rossettoy) , 2021-01-05 12:07
    Referenced by request #11397

    Other

    gerrit #21200
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2021-01-05 10:14
    last edited by: Yannis ROSSETTO (rossettoy) 2021-01-05 10:15
    Hello Geoffroy,

    A target field cannot be updated by the user directly, neither its type nor its values. The patch here will propagate to target fields an update done on a source field about type change (from SB to MSB for example) that can be done today on a source field but that is not propagated to target field.
    User avatar
    Geoffroy Grelot (ggrelot)2021-01-04 19:43
    Are you sure ? The source of a shared field would have a role of providing a set of reference values, while the clone field could be uni- or multi-select as per the target usecase, possibly different from the source usecase.
    User avatar
    Yannis ROSSETTO (rossettoy)2020-12-31 14:45
    last edited by: Yannis ROSSETTO (rossettoy) 2020-12-31 16:49
    Share field type change must be propagated to all target fields.
    • Status changed from New to Under implementation
    • Assigned to changed from None to Yannis ROSSETTO (rossettoy)