-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project List has a limit of 50 #955
Comments
I think I see the bug: In client_cloud.go ListProjects: https://github.com/mattermost/mattermost-plugin-jira/blob/master/server/client_cloud.go#L110 When limit = -1 to trigger the "fetchAll" behaviour, the revenant code is remaining := 50
...
for {
...
if len(result.Values) > remaining {
result.Values = result.Values[:remaining]
}
out = append(out, result.Values...)
remaining -= len(result.Values)
if !fetchAll && remaining == 0 {
// Got enough.
return out, nil
}
if len(result.Values) == 0 || result.IsLast {
// Ran out of results.
return out, nil
}
} When Changing remaining -= len(result.Values)
if !fetchAll && remaining == 0 {
// Got enough.
return out, nil
} to if !fetchAll {
remaining -= len(result.Values)
if remaining == 0 {
// Got enough.
return out, nil
}
} such that |
It's not only in the subscribe dialogue, it's also in the project dropdown when creating an issue. The limit is 50 there too and the autocomplete can only search through those 50 items. A PR would be much appreciated 🙏 |
…values (#67) * [MI-3466] Fix Jira issue mattermost#955: Save user's last used field values * [MI-3466] Code refactoring * [MI-3466] Fixed issue: not able to select prject while creating subscriptions * [MI-3466] Review fixes
The Project Dropdown in either attaching message to jira issue or creating subscription is limited to 50 records Possible solutions
|
This is biting my team as well. It looks like a related MR has already been merged. Can we get an update on when a fix for this will roll out? |
Hello, do we have any more information? This fix is eagerly awaited by my team too. |
Hello, It's can we have an update on that issues ? It's becoming urgent among my organization too. |
Hi, |
Is this something we can please get taken care of soon? Even a hard-coded bump in the limit of projects would be a big help. |
thanks for resolving this much appreciated |
* [MI-3466] Fix Jira issue #855: Save user's last used field values (#67) * [MI-3466] Fix Jira issue #955: Save user's last used field values * [MI-3466] Code refactoring * [MI-3466] Fixed issue: not able to select prject while creating subscriptions * [MI-3466] Review fixes * Review fix * [MI-3690] Removed the logic to save the component field
Our Jira instance has hundreds of projects and I am part of a group that has access to all of them.
When I try to use
/jira subscribe
only the first 50 projects are in the list, alphabetically. I am not able to scroll down to see the rest.Steps to Reproduce:
/Jira connect
in MM channel/Jira subscribe
in MM channelExpected Result: I can see all of the projects I have access to.
Actual Result: The project list ends at 50 projects.
Impact: Currently the only workaround to this is to create more Jira user groups with specific project access. Most likely won't be using this feature until this is resolved.
Please let me know if there is a better workaround available.
The text was updated successfully, but these errors were encountered: