You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Adaptavist instructions at
https://scriptrunner.adaptavist.com/latest/jira/script-fields/issue-picker.html
said that I can modify JQL query for custom field "Issue Picker" in Behaviours, by setting "field.setConfigParam('currentJql', '<your jql query>')".
I have tried to set field parameters in Behaviour, but the list of suggested issues in this field (it is called "Purchase order") does not change.
I used the code below in Behaviour:
getFieldByName("Purchase order").setConfigParam('currentJql', 'type=Task');
And when I open the screen with this custom field, it is suggested to choose issues by the query, that was defined when I create this field ('type=Bug'). But if I will choose the suggested issue, and will try to submit the form - I will receive an error, that I choose the wrong issue (not 'Type=Task').
So I just wonder - how I can change the JQL for custom field "Issue Picker" in behavior? (I need to do it in behavior, because I need to suggest different issue types based on issue custom field)
Any help would be appreciated!
Hi,
I am stuck at the same point right now.
I found out that when you start typing, the new jql query is applied. The new / filtered suggestion list is what you want. But if you clear the typed filter, you get the original list with the old jql again.
And if you select an issue, which does not match the query a validation error will occur.
So the only thing missing for this to work is, that the initial list of suggestions, with empty filter, is not updated with issues matching the new filter.
Maybe there is a way to trigger such a reload or modify the list by myself.
I found out that this is a bug, and at this moment all that we can do is just wait for a fix - https://productsupport.adaptavist.com/browse/SRJIRA-3119
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Александр Клюков @Robin Sadlo looks like this is now fixed as of ScriptRunner 5.5.3 (released in April 2019)!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
During my 17 years as a coach, mentor, and trainer of Agile teams, I’ve participated in hundreds of Agile planning meetings. The end result was a wall of backlog items annotated by an explosion of co...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.