How the Issue Picker Works from an End User's Perspective?
1. How Do End Users Pick Issues?
Required Jira Role: Jira Software USER
1.1 When is the Issue Picker Displayed for End Users?
The end user can utilize the Issue Picker under the following conditions:
The Issue Picker is included in the create and/or transition and/or edit screen.
The end user has permissions to create and edit the specific work item type
To use the issue picker correctly in the transition screen, please activate the New work transition experience
1.2 How the relevant Issues are listed in the Issue Picker?
The list of issues that the end user can select is dynamically generated by the app.
The app executes the Filter JQL as an admin and retrieves a list of issues.
This list can be limited to the current project if configured accordingly.
Initially, only the first batch of issues retrieved is displayed (subject to Atlassian's limitations).
To view additional issues, the end user must click 'more'."
We assume that no end user will scroll through thousands of options. In such cases, the end user will likely use the search function to narrow down the results. Therefore, we have decided not to retrieve all options and provide a paging function (The behaviour is similar to the standard field Fix Version/s). Fetching an extensive list of options could result in significant waiting times, especially when the option list is extensive.
1.3 How can the End User use the search function in the Issue Picker?
The End User can enter any text to narrow down the list of listed work items:
The app searches for the entered text in the Summary field to retrieve a subset of the listed work items.
The app also searches for exakt work item keys (A forecast search is planned, to list STORY-1 and STORY-10…. STORY-19, when STORY-1 is entered)
The search function of the app is based on the native search function of Atlassian, utilizing the JQL syntax. Therefore, the capabilities and limits are the same.
