You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is an Ejira issue or something configured company-side on the jira API, but when dealing with large projects ejira is only able to create a partial list of issues. I expect this to be either a limited request number issue or a pagination issue.
This has a knock on issue when loading one's own agenda, as if an issue returned by that jql query doesn't exist in the main org file then generating the agenda will fail. An initial entry for the unfound ticket seems to be created by this function, however ejira seems to fail with actually populating the properties for this entry, claiming that they cannot be found.
This can be worked around by adding more stringent search criteria to ejira-update-jql-unresolved-fn though this is a bit less ideal.
The text was updated successfully, but these errors were encountered:
JordanAnthonyKing
changed the title
Update my projects struggles for large projectsUpdate-my-projects struggles for large projects
Apr 18, 2021
JordanAnthonyKing
changed the title
Update-my-projects struggles for large projectsUpdate-my-projects doesn't get all issues for very large projects
Apr 18, 2021
I don't know if this is an Ejira issue or something configured company-side on the jira API, but when dealing with large projects ejira is only able to create a partial list of issues. I expect this to be either a limited request number issue or a pagination issue.
This has a knock on issue when loading one's own agenda, as if an issue returned by that jql query doesn't exist in the main org file then generating the agenda will fail. An initial entry for the unfound ticket seems to be created by this function, however ejira seems to fail with actually populating the properties for this entry, claiming that they cannot be found.
This can be worked around by adding more stringent search criteria to
ejira-update-jql-unresolved-fn
though this is a bit less ideal.The text was updated successfully, but these errors were encountered: