Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-50837

[ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

      When I select a value by filtering for the second time,it is replacing the value that was selected previously by using the filter with a different value.

       

      It means I am able to choose a value with filtering only once.

       

      Steps to reproduce:

      First create any freestyle or pipeline job with Active choice parameter and "Enable Filter" should be true

      1.Give some value to the filter and choose a value from the values that gets filtered out.

      2.Not give some other value to the filter and choose a value from the listed values.

      3.Now if you try to see the values that were selected by you, you can see only the last value that was selected. The old value might have been replaced by the new one.

          [JENKINS-50837] [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

          Saheta B added a comment -

          Hi, Any update on this?

          Saheta B added a comment - Hi, Any update on this?

          Pratik Jain added a comment -

          Ah!.. Now I saw that already there is a bug. I also raised the same bug here https://issues.jenkins-ci.org/browse/JENKINS-51054.

          Any update on this bug please

          Pratik Jain added a comment - Ah!.. Now I saw that already there is a bug. I also raised the same bug here https://issues.jenkins-ci.org/browse/JENKINS-51054 . Any update on this bug please

          Srinivas M added a comment -

          kinow,

          I am also facing same issue. Do you have any update on the resolution with ETA or any workaround fix for temporary?

          Based on my analysis, once I select item after entering a filter value and repeat it with number of selections with as many filter values, then clear the final value from filter text field before you trigger the build. It's holding all the items that are selected with all your previous filter options into the build parameter value.  If we can clear this field value before entering the build, then it might solve?

           

          Srinivas M added a comment - kinow , I am also facing same issue. Do you have any update on the resolution with ETA or any workaround fix for temporary? Based on my analysis, once I select item after entering a filter value and repeat it with number of selections with as many filter values, then clear the final value from filter text field before you trigger the build. It's holding all the items that are selected with all your previous filter options into the build parameter value.  If we can clear this field value before entering the build, then it might solve?  

          No updates from me. I'm currently overseas for a conference, back in July, will have some time with family before returning to $work. Then once I have time to work on Open Source will triage issues here to see what can be fixed and included in the next release.

          Closing this and the other duplicate issues, as there is an older issue for this already. Multiple issues make it harder to triage things and can be confusing to users too.

          This is not too complicated to fix, but requires a lot of patience and time, as it would require creating a state layer in JavaScript, with some sort of Stack/State, and link it with the choices selected... this can lead to multiple issues with different browsers, or different parameter types.

          Pull requests welcome! Always happy to review contributions by others and include in a future release. If there is urgency in this issue, please consider also hiring professional services, as there is a number of companies that offer Jenkins development (e.g. CloudBees, Praqma, most IT shops, and several Jenkins plugin maintainers), as most of the work here is maintained as Open Source volunteer work.

          Bruno P. Kinoshita added a comment - No updates from me. I'm currently overseas for a conference, back in July, will have some time with family before returning to $work. Then once I have time to work on Open Source will triage issues here to see what can be fixed and included in the next release. Closing this and the other duplicate issues, as there is an older issue for this already. Multiple issues make it harder to triage things and can be confusing to users too. This is not too complicated to fix, but requires a lot of patience and time, as it would require creating a state layer in JavaScript, with some sort of Stack/State, and link it with the choices selected... this can lead to multiple issues with different browsers, or different parameter types. Pull requests welcome! Always happy to review contributions by others and include in a future release. If there is urgency in this issue, please consider also hiring professional services, as there is a number of companies that offer Jenkins development (e.g. CloudBees, Praqma, most IT shops, and several Jenkins plugin maintainers), as most of the work here is maintained as Open Source volunteer work.

            kinow Bruno P. Kinoshita
            sahetab Saheta B
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: