Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-76042

"Could not find project with key XYZ" received when creating issues in MS Teams for Jira

XMLWordPrintable

      Issue Summary

      When creating issues from MS Team for Jira, user receives error "Could not find project with key XYZ" where

      XYZ stands for pkey of the first project in the Project List

      This happens when the user trying to create the issue does not have permission on the first project in the project list

      Steps to Reproduce

      1. Go to MS Teams for Jira
      2. Right Click on the message and Select Create Issue 
      3. You will receive an "Could not find project with key XYZ"

      Expected Results

      User should be able to create the issue

      Actual Results

      User receives an error: Could not find project with Key XYZ

      Workaround

      To workaround this issue, create a Dummy Project with name AAA (so that it is first entry in the project list) and give all users permission to this project. 

        1. Screenshot 2021-02-12 at 2.53.35 PM.png
          86 kB
          Apurva Rawat

            [JRACLOUD-76042] "Could not find project with key XYZ" received when creating issues in MS Teams for Jira

            Volodymyr Hensorskyi added a comment -

            The bug was reproducible on the previous version of MS Teams Jira Cloud integration. The flow works well in a new app.
            https://appsource.microsoft.com/en-us/product/office/WA200002140?tab=Overview

            Volodymyr Hensorskyi added a comment - The bug was reproducible on the previous version of MS Teams Jira Cloud integration. The flow works well in a new app. https://appsource.microsoft.com/en-us/product/office/WA200002140?tab=Overview

            Mohamed Darwiche added a comment -

            This workaround works, however you need to ensure the project appears at the top. So if you have a project with square brackets in the name, for example [xy], it will appear above AAA. In this scenario you'll need to name your project [AAA] and it will appear at the top. just make sure you create a company managed project and grant all users access. 

            Mohamed Darwiche added a comment - This workaround works, however you need to ensure the project appears at the top. So if you have a project with square brackets in the name, for example  [xy] , it will appear above AAA. In this scenario you'll need to name your project  [AAA] and it will appear at the top. just make sure you create a company managed project and grant all users access. 

            David Clark added a comment -

            The work around does not appear to work. The default project that is loaded is not alphabetically not at the top of the project list in Jira. So even though I created a sample project named 'AAA' with a project key 'AAA' it is not the project that is initially loaded into the Jira plugin/bot. Other users have different projects that seem to default in the plugin. But these projects are also locked down and/or the users do not have permissions to access or create issues. It is almost as if the plugin prefers to default to projects that the user does not have access to.

            David Clark added a comment - The work around does not appear to work. The default project that is loaded is not alphabetically not at the top of the project list in Jira. So even though I created a sample project named 'AAA' with a project key 'AAA' it is not the project that is initially loaded into the Jira plugin/bot. Other users have different projects that seem to default in the plugin. But these projects are also locked down and/or the users do not have permissions to access or create issues. It is almost as if the plugin prefers to default to projects that the user does not have access to.

            Marius Volkhart added a comment -

            We're seeing this for a project that has been deleted in JIRA, but the Teams integration is still trying to load it?

            Marius Volkhart added a comment - We're seeing this for a project that has been deleted in JIRA, but the Teams integration is still trying to load it?

              Unassigned Unassigned
              a79f4e2f4b7c Apurva Rawat
              Affected customers:
              19 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: