I am trying to use Jira expressions for a more complicated scenario and discovered that when ‘manually’ loading an issue - using new Issue(id) - the custom properties [issue type fields] are considered expensive operations. As such, I cannot include more than 5 new Issue operations and for each a custom property access.
However, when loading issues using jql - from context - I am able to load several custom properties for each issue, even if the jql returns more than 50 issues.
Could you please let me know if this inconsistency is by design ?
I cannot load the issues using jql in this case. I have to find them using the custom property info.