Try to create new issue in repo https://bitbucket.org/egrange/dwscript/issues but cannot, received message
As you can see in list of issues, last of them - i'm create few issues without any problems before, the last was in Feb'23.
I found few question with same problem, like https://community.atlassian.com/t5/Bitbucket-questions/I-can-t-create-any-issues/qaq-p/2305123 f.e., as per last messages by author - this problem solved only temporary, than coming again and again.
Any suggection or advices?
Hi @Vizit0r,
I reached out to our engineering team and they have fixed this. Could you please check if you can create a new issue in this issue tracker now?
Kind regards,
Theodora
@Vizit0r good to know that your problem was solved!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No this bug is not fixed. It is still affecting our public issue tracker.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Scott Wiltshire this has been fixed only for @Vizit0r and not for you. It would be great if you could create a new post about your problem and fill in all the necessary info. Thanx.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alex Koxaras _Relational_ this I understand. But this is clearly a general bug which has been introduced recently as part of the "upgrade" of Bitbucket permissions https://community.atlassian.com/t5/Bitbucket-articles/Taking-Bitbucket-permission-management-to-the-next-level/ba-p/2264892
However, a piecemeal approach by point-fixing individual repositories for what is clearly a general bug hardly seems like good practice!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with you. Did you raise a request to Atlassian about this? From the search I did on jira.atlassian, can't really find anything related. If you and the other who are facing this problem don't raise a request (and then vote/watch), I don't think that atlassian is going to put effort in solving this. So instead, if it affects a few people, it might solve it individually.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vizit0r and welcome to the community,
I'll escalate internally your issue, and a member of the Atlassian team will contact you.
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.