Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-22183

The Jira macro cannot find a Jira project that has alphanumeric characers within its project key.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 4.1.3
    • 3.5.1
    • None
    • Development - Linux

      JDK 1.6 - Confluence Standalone Tomcat - OS: Linux

      Here is an example of my problem if I try to view the first issue of the "D8" project:

      {jira:D8-1|server=Company Issue Tracking}

      The macro above yields the following result:

      "The JIRA server was not able to process the search. This may indicate a problem with the syntax of this macro..."

      However, if I create a project with a key "DD", the following example works great:

      {jira:DD-1|server=Company Issue Tracking}

      Apparently, it's the numeric values within the project key that stop the Jira Connector from seeing anyting with that project.

            [CONFSERVER-22183] The Jira macro cannot find a Jira project that has alphanumeric characers within its project key.

            Paul Curren added a comment - Knowledge Base article created: http://confluence.atlassian.com/display/CONFKB/The+JIRA+macro+fails+for+JIRA+projects+with+numbers+in+the+project+key

            ChrisM added a comment -

            Just for the sake of completeness: The new "Autoconvert for Links"-feature in Confluence 4.1 does of course NOT work with links to issues which contain numbers in their key.

            ChrisM added a comment - Just for the sake of completeness: The new "Autoconvert for Links"-feature in Confluence 4.1 does of course NOT work with links to issues which contain numbers in their key.

            Our company is looking to start using Confluence however two of our JIRA project keys are "RV5" and "RV4" so this problem is preventing us from integrating JIRA and Confluence. Until this issue is resolved our company cannot purchase Confluence. Please fix this issue as soon as possible.

            Robin Knox added a comment - Our company is looking to start using Confluence however two of our JIRA project keys are "RV5" and "RV4" so this problem is preventing us from integrating JIRA and Confluence. Until this issue is resolved our company cannot purchase Confluence. Please fix this issue as soon as possible.

            I have encountered the same behavior. We use Confluence 4.0. and JIRA 4.4.
            The integration (issue embeding in Conflu.) works fine for the projects without numbers in their projectkey, but doesnt work at all otherwise (Conflu. displays table with text saying:
            "The jira server was not able to process the search. This may indicate a problem with the syntax of this macro. Alternatively, if this macro is requesting specific issue keys, you may not have permissions to wiew one of these issues."

            We have multiple projects with projectkeys containing numbers, so the integration with Confluence doesnt work for us at all.

            Please fix asap.

            Petr Holodňák added a comment - I have encountered the same behavior. We use Confluence 4.0. and JIRA 4.4. The integration (issue embeding in Conflu.) works fine for the projects without numbers in their projectkey, but doesnt work at all otherwise (Conflu. displays table with text saying: "The jira server was not able to process the search. This may indicate a problem with the syntax of this macro. Alternatively, if this macro is requesting specific issue keys, you may not have permissions to wiew one of these issues." We have multiple projects with projectkeys containing numbers, so the integration with Confluence doesnt work for us at all. Please fix asap.

            We have same issue. Please fix this ASAP.

            Deleted Account (Inactive) added a comment - We have same issue. Please fix this ASAP.

            Ubong, that fix is for Jira NOT Confluence. I agree with Eddie that this is an issue with Confluence and the Jira Macro within Confluence that does not support alphanumeric values for project keys. I hope this gets resolved soon as most of our project keys in Jira are alphanumeric and the integration with Confluence doesn't exist without this support.

            Ron Dinwiddie added a comment - Ubong, that fix is for Jira NOT Confluence. I agree with Eddie that this is an issue with Confluence and the Jira Macro within Confluence that does not support alphanumeric values for project keys. I hope this gets resolved soon as most of our project keys in Jira are alphanumeric and the integration with Confluence doesn't exist without this support.

            ubong ekpe added a comment -

            Hi,

            We had a similar problem when we upgraded to jira 4.3.4. We were unable to search for issues with project keys that had numbers in them. After some investigation we realized that this was due to the jira.projectkey.pattern setting in the jira-application.properties file. Once we changed the value from jira.projectkey.pattern = ([A-Z][A-Z]) to jira.projectkey.pattern = ([A-Z][A-Z0-9]) and rebooted the instance, the problem was resolved. Maybe that will work for you too if you haven't resolved this already.

            – Ubong

            ubong ekpe added a comment - Hi, We had a similar problem when we upgraded to jira 4.3.4. We were unable to search for issues with project keys that had numbers in them. After some investigation we realized that this was due to the jira.projectkey.pattern setting in the jira-application.properties file. Once we changed the value from jira.projectkey.pattern = ( [A-Z] [A-Z] ) to jira.projectkey.pattern = ( [A-Z] [A-Z0-9] ) and rebooted the instance, the problem was resolved. Maybe that will work for you too if you haven't resolved this already. – Ubong

              pcurren Paul Curren
              527feab301ff Eddie Connatser
              Affected customers:
              15 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: