We have migrated the JIRA server to JIRA cloud few months back. We have been trying to integrate Slack with JIRA cloud recently. However, we experience an issue when trying to connect the Projects which were migrated from old JIRA version to new cloud. Even though the integration has done properly with this projects migrated it does not allow to read JIRA issues from Slack (Except for some Sub-Tasks). The Sub-Tasks created under the old Task that were migrated are readable through Slack command without any issue. But not all the Sub-Tasks are readable. However, still you can create the issues through Slack in this same project.
The migration was initially done from JIRA server 5.0 version to 7.0 before migrating to Cloud JIRA.
Please note that this issue is existing only for the projects migrated. The projects we created newly in the cloud has no issue after the integration with Slack. We checked all our permission schemes and none of them seem to have any issue to not allow read JIRA issues, given the create option through Slack works fine. When type /jira <IssueID> it says Issue not found only to the old projects (A screenshot is attached)
What could be the workaround to overcome this issue?
Hi @savani , welcome to the Community!
I understand you are having some trouble getting the Slack integration to read info from tickets that were a part of your Cloud migration, even though it seems to work correctly with new projects. Unfortunately it looks like your screenshot wasn't uploaded to your post, but I think I have an idea of what might be the problem.
For the projects you migrated from your Server instance, it's possible the atlassian-addons-project-access project role is missing from the Browse and Administer project permissions. Here's how to resolve that:
Let me know if you see any more trouble after completing the permission changes above and we'll help get you squared away!
Daniel | Atlassian Support
Hi @Daniel Eads
Thanks for the prompt respond.
The screenshot which has the error when trying to read the issues from JIRA is attached herewith.
Further, with regards to the solution you have given, atlassian-addons-project-access project role has been already assigned for the Browse and Administer project permissions as shown in the image below. Still we had the issue which indicates the problem is not with the assignment of project role.
We tried out every possible way to resolve this. We changed the permission scheme same as a new project we created and still the old projects have the issue. Kindly look into this and provide us with a solution to successfully integrate the Slack with old projects.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event