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

0 vue
Accéder directement au premier message non lu

bsaheta@gmail.com (JIRA)

non lue,
17 avr. 2018, 04:25:0317/04/2018
à jenkinsc...@googlegroups.com
Saheta B updated an issue
 
Jenkins / Bug JENKINS-50837
[ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
Change By: Saheta B
Summary: [ActiveChoicePlugin] FIlter is not working properly when I install with the ActiveChoice plugin version 1.5.3
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

bsaheta@gmail.com (JIRA)

non lue,
17 avr. 2018, 13:06:0317/04/2018
à jenkinsc...@googlegroups.com
Saheta B updated an issue
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.

bsaheta@gmail.com (JIRA)

non lue,
23 avr. 2018, 03:31:0123/04/2018
à jenkinsc...@googlegroups.com

bsaheta@gmail.com (JIRA)

non lue,
25 avr. 2018, 07:19:0325/04/2018
à jenkinsc...@googlegroups.com

jainpratik25@gmail.com (JIRA)

non lue,
1 mai 2018, 06:23:0201/05/2018
à jenkinsc...@googlegroups.com
Pratik Jain commented on Bug JENKINS-50837
 
Re: [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

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

imoutsatsos@msn.com (JIRA)

non lue,
14 mai 2018, 09:43:0314/05/2018
à jenkinsc...@googlegroups.com

imoutsatsos@msn.com (JIRA)

non lue,
14 mai 2018, 09:43:0314/05/2018
à jenkinsc...@googlegroups.com

bsaheta@gmail.com (JIRA)

non lue,
26 févr. 2019, 00:33:0226/02/2019
à jenkinsc...@googlegroups.com
Saheta B updated an issue
Change By: Saheta B
Priority: Minor Critical
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

m.srinivaschary@gmail.com (JIRA)

non lue,
12 juin 2019, 06:01:0212/06/2019
à jenkinsc...@googlegroups.com
Srinivas M commented on Improvement JENKINS-50837
 
Re: [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

Bruno P. Kinoshita,

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?

 

brunodepaulak@yahoo.com.br (JIRA)

non lue,
12 juin 2019, 20:32:0312/06/2019
à jenkinsc...@googlegroups.com

brunodepaulak@yahoo.com.br (JIRA)

non lue,
12 juin 2019, 20:32:0412/06/2019
à jenkinsc...@googlegroups.com
Bruno P. Kinoshita commented on Improvement JENKINS-50837
 
Re: [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

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.

Répondre à tous
Répondre à l'auteur
Transférer
0 nouveau message