I'm trying to create JIRA issues from Confluence. My requirements are defined in the table and I'm using functionality "Create JIRA issue" with possibility to create multiple issues.
This creation works fine when the table contains 9 lines, but seems if there is 10 or more lines in the table then issues in JIRA are created but JIRA links are not propagated into CONFLUENCE. I got also Error message.(The server may be unreachable. Please ensure you are running JIRA 5.0 or higher.)
We have JIRA 7.6.12.
Is there any limitation for creation JIRA issues from Confluence?
Something like number of records or cumulative number of characters, not allowed special characters like #, _, ... or any other limitation which we should take into account while using this feature?
Thanks for your advices,
Amalia
Hello @Amalia Dobiasova
Is this still an issue for you?
If so, I have looked into this issue as it is specific, the creation of 10 issues or higher from within Confluence does not render the issue links in the table.
There is a known issue with creating multiple issue though it does not account for a specific limit unfortunately. This issue is known on Confluence Cloud, not Server, are you running Confluence server? What Confluence version are you running?
With regards to limitations of the Jira Issue Macro, there is documentation though nothing I can specifically find that would limit issue creation rendering.
You could check out the documented Confluence bugs on Atlassian's Jira to see if there is something that relates to issue, I had a look myself and could not find anything that met your requirements.
Hope this helps,
Danny
Hello Danny,
Issue is still there. We have a server. We are not in the cloud.
I have reported issue also to our IT deparment, so maybe they are already in contact with Atlasian.
Just to be clear in our case issues are created in JIRA but links are not propagated to Confluence page and I got an error message: The server may be unreachable. Please ensure you are running JIRA 5.0 or higher.
Thanks for links above, I will chek it.
Regards,
Amalia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have had the same issue and the issue has been reported on Cloud and Server. I would check that your IT dept has reached out to Atlassian support directly as they may be able to give you a workaround.
Hope this gets sorted for you.
Thanks,
Danny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.