-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
When creating a new Plan based on a filter, Advanced Roadmaps for Jira uses the below REST API call to populate the list of available filters:
GET <JIRA_BASE_URL>/rest/jpo/1.0/filters
The call fetches only 50 filters and then populates these in the drop down list.
Upon typing more characters in the name of the filter, more calls are made to the above REST call using the parameter ?name=<typed_characters> until you are satisfied with the search results.
The limit of the above calls is still 5 filters per result from each call.
The problem would be if the user typed a part of a filter name and the results would be more than the 50 filters displayed, this, we would have matching filters that wouldn't be dispalyed.
If the user don'ts know the exact filter name, or if the user doesn't remember the name of the filter and it could happen that he can't find the filter as it is not displayed in the selection list.
This scenario is more likely on larger instances that contains a large amount of filters per user.
It might be better to allow Jira admin to configure the maximum value of retrieved filters, or to allow a button to use another call to bring in more results if more are found in the drop down list.
- links to
- mentioned in
-
Page Failed to load
Form Name |
---|
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC