I am on premium plan because we want to enforce the required checks.
For some reason a developer was able to merge the pull request when only 2 of the requests passed.
After hearing back from support it seems the solution was to not use patterns in the naming as that may not be working properly.
The pattern used is not standard Regex but some other version, so originally was recommended to use (develop,main) as (develop|main) is not valid and would never trigger any check. This triggered the check but appears it didn't enforce the merge restriction from being allowed.
Atlassian solution was to create separate checks for each branch naming even with the exact same parameters. It appears to be working properly.
Our workspace is also on the Premium, and tested it just now. I cannot merge if merge checks fail -- meaning it isn't a global problem.
Hm, I noticed this other question where the poster complains about the Premium features not being available. It resembles to your case and thus may be something with the platform, have you opened a ticket for Atlassian?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The premium features are available but I haven't opened a ticket with Atlassian. They seem to force bad AI in front of it so I thought the community may be able to help beforehand.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have Prevent a merge with unresolved merge checks option enabled, or maybe it was disabled at the time it was merged?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.