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.
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-fnthough this is a bit less ideal.