Confluence does not respect the selected application when creating an issue through the JIRA Issues Macro.

When Confluence has Application Links created for more than one JIRA, if the user tries to create a new issue through JIRA Issues Macro on the JIRA that is not set to primary on the applinks list, Confluence actually creates the issue on the primary JIRA instead.

Also, if both projects (from Primary JIRA and the other JIRA) have different types for issues, the creation button won't work, keeping Confluence on the same screen.

Steps to reproduce:

1. Install 2 JIRA 6.2.3 instances
   On JIRA 1
2. Create a new Software Development project called "Project1"
   On JIRA 2
3. Create a new Simple Issue Tracking project called "Project2"
   The Project Type does not matter, we just need to create a custom Issue Type
4. On JIRA2. create a custom Issue Type called "new", for example
5. Now, install a Confluence 5.6.3
6. Create the application links between Confluence and those 2 JIRA instances
7. Set JIRA1 to primary on Confluence's applinks list
8. Create a page on Confluence
9. Insert the JIRA Issues Macro
10. Create a new issue
11. Server = JIRA1, Project = Project1, issue type = Bug, fill in summary and description
12. Click insert
    • Issue is created and displayed on page
13. Save the page
14. Edit the page
15. Insert the JIRA Issues Macro
16. Create a new issue
17. Server = JIRA2, Project = Project2, issue type = new, fill in summary
18. Click on insert
    • No response - popup still open, nothing changed
19. Change issue type to New Feature, fill in summary
20. Click on insert
    • The issue is inserted, however, if you look at this just created issue, it was actually created on JIRA1 (Project1) instead of JIRA2 (Project2)

Also, another issue related to this bug is if the secondary JIRA (JIRA2) has 2 projects while the primary JIRA (JIRA1) has only one. If the user selects the second project, Confluence shows a red error text: "Project is required"