Pramodh M Community Champion

When you create App passwords is not to define what the user can do to your repo but rather what they can do to the objects that they have access. You still have control over your repository on what the users can do, you are giving them the write access that's all. Even if they create an App password selecting all the…

They can only use it for your repo, if you give them the access via "Users and Groups access" otherwise no, they can't Yes, the part where you mentioned the access is based on what access you have given in your repo. So if you have given the user as Write access, they will have write access, they will only be able to pull…

Okay Here's the catch. They can use the HTTPS URL of the repo, and for authentication let them use their accounts App password, don't share your accounts' App key. App key is associated with the Account, not the repository.

FYI

Okay, I got it. @Bitwise DEVS So you need to give them full access to the repo? Here's the reference. Give them the Write access as specified here That should work

Hi @Bitwise DEVS App Password for one thing is used for Authentication with remote repo or API's Well, the Secure part depends on how the scope is given if you are okay with your repo being exposed when your App token is shared, that's okay. And yes, you can revoke it but why manage those access with APIs when you can…

Hi @Bitwise DEVS Never ever share App Passwords!! Ask them the SSH Public key and add it in your repo to give them the write access, go with 1st Option. Or you have an option to invite them as well If you need to restrict the Branch Permissions, you can do it in branch permissions under the settings of the repository Let…

FYI I just created a Pipeline in my account with private access, I was able to run it. May be if you are using the Bitbucket pipelines feature extensively, that is causing it to enable the SSH Keys

Thanks @Bitwise DEVS Yep, @Theodora Boudale has given the reason in the thread!! This is it. To prevent abuse from misusing the Pipelines feature, these are some pre-checks that they have implemented. So go ahead and enable SSH Key, 2FA on your account which makes it secure!! Let me know if you have need any clarification.…

Maybe your workspace admin has made it required for the repos in your workspace Try enabling 2FA and then running the pipelines?

No @Bitwise DEVS We don't need a 2FA or SSH key to run pipelines!! We need an SSH key in order to enable 2FA. Can you please confirm whether you have added the SSH key? Or try with adding an SSH Key and updating the 2FA setting, then work with repos you have in your workspace and all is working well and confirm once

Yes, then 2FA is the reason!!

Hi @Bitwise DEVS There's no setting like that! Maybe your workspace is enforced to have 2FA in place which is causing this result Here's a public repo I just tested it out without SSH Key --> Link here May I know the Bitbucket pipelines you have enabled has some tasks related to SSH Authentication? Thanks, Pramodh

Hi @Nwumfor James Welcome to the Community!!

Hi @Alex Shirokov Yeah Cloning would be a good option If you go with Automation, what is the link with Epic 1 when you create Epic 2. If you have input here, let me know Thanks, Pramodh

@Matthew Knatz Yeah that is the reason, have the resolution unset in the transition, that should work. Having a resolution in Workflow set at the end is good practice, and we should clear if it is on other status other than what we recognise as done 

It makes sure for every step, you have the defined steps checked Say if the blocked issue is transitioned, it makes sure that it has linked issue Then for the linked issue, it checks all the blocked issues are in done status!!

Hi @Gary DeJarnett You should have written mail in advance to let them know so that the team will be aware of the situation, and maybe by trial methods, they would have given some more time. Anyways, make sure to don't ignore the payments or communicate with the Atlassian team in advance going forward. Have you created a…

Hi @Ben Stolman I know the automation is working, but as I said this may introduce a bug, can you try the below Automation and let me know if its works? JQL - You limit this to project by adding AND project = project-key Thanks, Pramodh

@Ben Stolman This may introduce a bug if you have linked an issue from a blocked issue to another issue with relation "blocked by" And we have to keep an eye on the number of automation that it runs!!

Oh I read the text wrong way, yeah correct it's not possible 😅

@roman_romanenkov May I know why you are taking hard route to get the page id in confluence when you have the better way of taking page id from API or just the URL

Yes Correct @AtlassianAdmin !!

Hi @roman_romanenkov You will get the page id while you are on confluence page itself Let's say you are on the specific page, the URL field would look something like this https://your-site.atlassian.net/wiki/spaces/MTS/pages/27066369/Page+1 Here 27066369 is your Page id Let me know if you need further assistance Thanks,…

Hi @Зелянин Виктор Welcome to the community 🙂 There is no direct way to remove the labels from confluence, but you can try the below plugin https://marketplace.atlassian.com/apps/1211162/labels-cage Here's the reference https://community.atlassian.com/t5/Confluence-Cloud-questions/delete-labels/qaq-p/988106 Thanks, Pramodh

HI @青山 明 First check the space permissions and then have page restrictions. Manually check the permission is working and then use same users/groups you have used via API. Let me know if you need specific API whether it's space permission or page restrictions Thanks, Pramodh

Atlassian team, this user has created multiple tickets on creating 300+ repositories, this may be spam. Please look into it

Why are you creating multiple tickets? Is this a spam

It works similar to the one with Reset approvals when the source branch is modified If there are any changes to the source branch of the pull request, the pull request updates with no request changes and the reviewers have to review and approve the pull request again.

FYI The link is just for example, Modify this to include Transition Issue trigger and the Action as send slack message