I can't create any issues?
Asked by Rakete:

I want to create an issue in a public project. I can't. I always get a page telling me I am not allowed to do that:

We can't let you see this page {#toc-hId--471554420}
----------------------------------------------------

The project has a public issue tracker, I can see other people creating issues and I have created issues in that project before myself.

I tried creating my own project and creating an issue inside, that worked.

The project where I can't create any issues is this one: <https://bitbucket.org/Diffeomorphic/import_daz/src/master/>

Any suggestions what could be the problem?


Answers:
author: Patrik S
body: Hello [@Rakete](/t5/user/viewprofilepage/user-id/5175058) ,

Thanks for reaching out to Atlassian Community!

I went ahead and created an internal support ticket using the email of your community account so we can look into this issue. You should be receiving an e-mail soon with the ticket link, but in case you don't receive it, please let me know so I can share the ticket link here.

Thank you, [@Rakete](/t5/user/viewprofilepage/user-id/5175058) !

Patrik S

comments: author: Rakete
body: The problem solved itself in the meantime. I can now create issues again.


author: Patrik S
body: Thanks for letting us know and glad to hear you are able to create issues as usual again :)

In this case, feel free to reach out to the community in case you need further assistance in the future!

Thank you, [@Rakete](/t5/user/viewprofilepage/user-id/5175058) !

Patrik S


author: Rakete
body: The problem is actually back. And now there is not only me complaining about not being able to create new issues.

Me complaining here: <https://bitbucket.org/Diffeomorphic/import_daz/issues/1470/new-buildbaked-function-not-working-for>

Someone else complaining here: <https://bitbucket.org/Diffeomorphic/import_daz/issues/1450/advanced-morphs-update-slider-limit-doesnt>


author: Diffeomorphic
body: I am the owner of this repo, and I can confirm the problem. I have no problems when I am logged in with my regular account, where I am the admin of the repo, but when I created a new account I was unable to neither create new issues nor to comment. However, I could attach a file and write a comment that way.


author: Patrik S
body: Hello [@Rakete](/t5/user/viewprofilepage/user-id/5175058) [@Diffeomorphic](/t5/user/viewprofilepage/user-id/3657440) ,

I've reached out to you using the internal ticket I had previously created. You should be receiving an email with my update and the ticket number. In case you don't receive it, please let me know so I can share the ticket link here.

Thank you!

Patrik S


author: Scott Wiltshire
body: This issue is anything but "solved". We have a public issue tracker and it's important that our customers and partners can raise bug and ER issues. Currently unless the bitbucket login is a team member of the repository the user can't create an issue. \*\*this needs to be fixed urgently\*\*.

I guess it is related to the rollout of "enhanced permissions" <https://community.atlassian.com/t5/Bitbucket-articles/Taking-Bitbucket-permission-management-to-the-next-level/ba-p/2264892>

But guys, seriously, how about some testing?


author: Patrik S
body: Hello [@Scott Wiltshire](/t5/user/viewprofilepage/user-id/1849056) ,

Would it be possible for you to share here the link to the Issue tracker where you are facing this issue? If you don't want to share it here in a public forum, let me know so I can raise an internal ticket for you.

Thank you, [@Scott Wiltshire](/t5/user/viewprofilepage/user-id/1849056) !

Patrik S


author: Martin Pala
body: The same problem is for example in this Issue tracker: <https://bitbucket.org/tildeslash/monit/issues>

The problem started ca. one month ago (March 2023): Somebody was spamming the Issue tracker, we have switched it to the Private mode, and then back to Public after few days. After that, existing users who were able to create Issues (e.g. [@LutzMad](/t5/user/viewprofilepage/user-id/5191321) ) are no longer able to create issues and are facing exactly the same symptoms, as described in this forum.

Maybe the transition Public-\>Private and Private-\>Public triggered the problem?


author: Patrik S
body: Hey [@Martin Pala](/t5/user/viewprofilepage/user-id/2337013) ,

Thank you for reporting that!

Our engineering team has identified the problem that caused this, and they have deployed a fix. Could you please check with the users if they can create a new issue for this issue tracker now ?


author: Scott Wiltshire
body: [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) I have created a ticket for this issue [BBS-201303](https://support.atlassian.com/requests/BBS-201303) the details are on the ticket. There is no resolution as yet


author: Martin Pala
body: Thanks [@Patrik S](/t5/user/viewprofilepage/user-id/4603309), it seems the solution for new issues works - Lutz did test the Issue tracker and it seems he's able to create new issues again.

However, he still cannot add new comments nor edit comments, which he previously made to old issues - it seems there is still some access control problem.


author: Patrik S
body: Hello [@Martin Pala](/t5/user/viewprofilepage/user-id/2337013) ,

You're very welcome!

As for the other issue where the user was not able to add a comment to existing issues, could you ask the user to try again? I've shared this with our engineering team and they have implemented a fix for it as well.


author: MDT Technical Asgar
body: Civil work management

comments: author: Rakete
body: This does not help me.


Tags: bitbucket-cloud

cloud