Hi all,
Just sharing a notice that we’ve discovered (and Atlassian confirmed) a bug in the IssueContents connect module loader where it may load the issueContents panel for the wrong Jira issue. This happens when the user navigates using linked issues.
When this happens Jira will load the app issueContext panel and pass in the wrong context variables in the query string. e.g. {issue.key} will be wrong. Also the AP.context.getContext() calls return the wrong issue.
Atlassian has raised this as bug ECO-156. If your apps use issue context panels this will probably affect you. Showing data for the wrong issue is a significant problem. Consider throwing a vote on ECO-156 to help encourage Atlassian to fix this ASAP.
Regards,
Chris C.
Digital Rose