youngmon/atlassian-qna huggingface dataset:
Linking together automation on requester email domain, organisation creation and portal restriction
Asked by Paula Lyon-Lee:

So here is what I want to happen,  

Support request is submitted via email  
Service project receives the email  
creates a ticket -(everything up to this point is working correctly)

<br />

use the requester email domain to determine the organisation  
creates the organisation if it does not exist  
Adds the user to the organisation  
adds the ticket to the organisation  
populates the Organisations field on the ticket.  

I just can't get it all working together.

<br />

I also have this setting set to no because I do not want users to be able to see each others tickets in the portal if they register  

##### Should new requests automatically be shared with a customer's organization? {#toc-hId--1450981295}

No, don't share email requests with the customer's organization. Requests sent from the portal will not be shared unless the customer selects otherwise


Answers:
author: Joseph Chung Yin
body: [@Paula Lyon-Lee](/t5/user/viewprofilepage/user-id/5158421) -

Need to confirm that "I just can't get it all working together. " means you have all the rules established and working, but it is not working as expected where the first rule at Issue Created trigger is not triggering the org creation?

Please advise. On the other hand, I am not aware that there is an action that will create the organization objects. I believe you will need to use the action "Send Webhook" with the correct REST APIs call and JSON body to conduct the setup. I have not personally done that yet at this time.

Looking forward to your reply.

Best, Joseph Chung Yin

comments: author: Paula Lyon-Lee
body: Hello and thank you for the quick response.  

I believe I have set thing up correctly.  

I have organisations with domains registered to them to capture new customers.  
When a new customer emails a request they correctly get added to the organisation and I can see the request listed for the organisation.  

The issue is that the tickets Organisations field is not being populated.  

I have tried creating an automation rule that triggers when an issue is created and the action is Edit issue -\> set Organisations -\> Use reporters e-mail domain  
with the option to create the organisation if it doesn't exist  

I also do not want requesters to see each others requests even if they are in the same organisation.  

<br />

I also need the email domain of the organisation to be set as well if thats possible  


Tags: cloud

jira-service-management

jira-service-management-cloud
Bitbucket pipeline error while executing Sonar Qube and the project uses JFrog Artifactory server.
Asked by Daniel Fuentes:

1. I have a Maven project in Bitbucket (Cloud). In the POM file, I have configured the following dependency:  

   ![f9n5AXi32V.png](/t5/image/serverpage/image-id/294532i849B46A84F73148B/image-size/large?v=v2&px=999 "f9n5AXi32V.png")
2. I have a bitbucket pipeline configured that runs the SonarQube code analysis. But it was running ok a few days ago. Until the JFrog server was created a newer version of this dependency "**0.0.1-20231117.235019-16**"
3. Now my pipeline is failing, and in the logs, I'm seeing that the step of calling the Sonar Qube analysis is downloading the newest dependency.  

   ![Ce5r2CPp1X.png](/t5/image/serverpage/image-id/294533i99C9C247389FAEB9/image-size/large?v=v2&px=999 "Ce5r2CPp1X.png")
4. In the logs I see that maven downloaded the maven-metadata.xml file from the JFrog repository and in that file has the newest version configured.
5. This is my bitbucket-pipeline.yml file.  
   ![YASolpzrzY.png](/t5/image/serverpage/image-id/294534iEC9C3223495CAEBA/image-size/large?v=v2&px=999 "YASolpzrzY.png")

Does anyone has any idea what can I do in order to fix this?


Answers:
author: Patrik S
body: Hello [@Daniel Fuentes](/t5/user/viewprofilepage/user-id/1657049) and thank you for reaching out to the Community!

I see from your pipeline YML that you are using maven caches. It might be the case that maven is getting that version from a previous cache that was generated in your pipeline.

To check if this is the issue, you can try manually clearing the cache by following the below steps:

* Navigate to **Pipelines** page
* Click on the **Caches** button on the top right side of the page
* Delete any **maven** cache using the **trash icon** right after the cache name.

Once the cache is deleted, you can try to run your build again and see how it goes.

If the error persists, it's also possible that one of your other dependencies required the new version of Jfrog, which is making Maven download it. I found [this thread in Stackoverflow](https://stackoverflow.com/a/19565587) which suggests the command below to check the dependency tree for any other dependency that requires jFrog :

```
mvn -Dverbose=true dependency:tree
```

Hope that helps!

Thank you, [@Daniel Fuentes](/t5/user/viewprofilepage/user-id/1657049) !

Patrik S


Tags: bitbucket-cloud

cloud
I can't add an assignee to our BitBucket issues. How do I fix this?
Asked by trekhopton:

When I go to add an assignee to a BitBucket issue, I start typing the name of the desired assignee but nothing shows up. It just shows "Searching..." forever.

If I create the issue then go back to edit it, it does the same.


Answers:
author: trekhopton
body: ![Screenshot from 2023-11-30 09-36-38.png](https://community.atlassian.com/t5/image/serverpage/image-id/294530i797CA3C701F106D1/image-size/large?v=v2&px=999 "Screenshot from 2023-11-30 09-36-38.png")![Screenshot from 2023-11-30 09-41-01.png](https://community.atlassian.com/t5/image/serverpage/image-id/294531i7500712D4CEDE63D/image-size/large?v=v2&px=999 "Screenshot from 2023-11-30 09-41-01.png")

Even common names that would have many account results don't yield results.

comments: author: Patrik S
body: Hello [@trekhopton](/t5/user/viewprofilepage/user-id/5104124) and thank you for reaching out to Community!

Could you share with us the **masked** **name** of the workspace and repository affected so we can investigate what might be happening?

For example, the repository my_workspace/my_repo would become m\*\*\*\*\*\*\*\*ace/m\*\*\*\*po.

Thank you, [@trekhopton](/t5/user/viewprofilepage/user-id/5104124) !

Patrik S


Tags: bitbucket-cloud

cloud
? Error waiting for deployment successful: Waiter DeploymentSuccessful failed
Asked by Suhail Ansari:

? Error waiting for deployment successful: Waiter DeploymentSuccessful failed: Waiter encountered a terminal failure state: For expression "deploymentInfo.status" we matched expected path: "Failed"  
100.  
INFO: {'deploymentInfo': {'applicationName': '$APPLICATION_NAME', 'deploymentGroupName': '$DEPLOYMENT_GROUP', 'deploymentConfigName': 'CodeDeployDefault.AllAtOnce', 'deploymentId': 'd-7ZZ0YWY01', 'revision': {'revisionType': 'S3', 's3Location': {'bucket': '$S3_BUCKET', 'key': 'suhail-cicd-1-2f9c46a2', 'bundleType': 'zip'}}, 'status': 'Failed', 'errorInformation': {'code': 'HEALTH_CONSTRAINTS', 'message': 'The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems.'}  
I have been trying to upload S3 image through aws cloud deploy, here's my yml  
image: atlassian/default-image:2

pipelines:  
pull-requests:  
"\*\*":  
- step:  
max-time: 120  
size: 1x  
script:  
- npm test  
trigger: automatic  
branches:  
deployment:  
- step:  
name: Build  
script:  
- zip -r production.zip \*  
artifacts:  
- production.zip  
- step:  
name: Upload to S3  
services:  
- docker  
script:  
- pipe: atlassian/aws-code-deploy:1.4.0  
variables:  
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID  
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY  
AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION  
S3_BUCKET: $S3_BUCKET  
COMMAND: "upload"  
APPLICATION_NAME: $APPLICATION_NAME  
ZIP_FILE: "production.zip"  
- step:  
name: Deploy with CodeDeploy  
services:  
- docker  
script:  
- echo "Environment ${REPOSITORY_VARIABLE}"  
- pipe: atlassian/aws-code-deploy:1.4.0  
variables:  
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID  
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY  
AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION  
S3_BUCKET: $S3_BUCKET  
COMMAND: "deploy"  
APPLICATION_NAME: $APPLICATION_NAME  
DEPLOYMENT_GROUP: $DEPLOYMENT_GROUP  
IGNORE_APPLICATION_STOP_FAILURES: "true"  
FILE_EXISTS_BEHAVIOR: "OVERWRITE"  
WAIT: "true"


Answers:
author: Igor Stoyanov
body: Hi [@Suhail Ansari](/t5/user/viewprofilepage/user-id/5375529) . Please, [check this answer](https://community.atlassian.com/t5/Bitbucket-questions/The-overall-deployment-failed-because-too-many-individual/qaq-p/2469335).  

Regards, Igor


Tags: bitbucket-cloud

cloud
Bitbucket Issues: return key does not work in textareas
Asked by benish:

When editing or creating a Bitbucket Issue the return key does not work in textareas -- that is, hitting the return key does not create a new line. My return key works in all my other apps -- in fact...

it works in this textarea.

I've tried in Chrome, Firefox, and Safari, and it's broken in all 3.

Every time I hit \`return\` I get this in the browser Console: <https://go.benish.io/GCrZkGb9>

\`\`\`  
Uncaught TypeError: (0 , a.isCapsLockOnAndModifyKeyboardEvent) is not a function  
at n.handleKeyDown (41.js:96:1797733)  
at vendor.js:463:62035  
at e.value (vendor.js:463:101410)  
at Et.keydown (vendor.js:463:61990)  
at e.dom.addEventListener.e.input.eventHandlers.\<computed\> (vendor.js:463:97039)  
at HTMLDivElement.nrWrapper (54:41:16224)

Uncaught TypeError: (0 , a.isCapsLockOnAndModifyKeyboardEvent) is not a function  
at n.handleKeyDown (41.js:96:1797733)  
at vendor.js:463:93056  
at e.value (vendor.js:463:101410)  
at wn (vendor.js:463:93011)  
at e.handleDOMChange (vendor.js:463:96657)  
at e.value (vendor.js:463:87335)  
at MutationObserver.\<anonymous\> (vendor.js:463:83692)  
\`\`\`

This really seems more of a bug report than a question anyone else needs to see, but when I tried to submit a bug report it sent me here. Not sure why you wouldn't want people to submit bug reports, but here we are.


Answers:
author: Mark C
body: Hi [@benish](/t5/user/viewprofilepage/user-id/1807653) ,  

Thank you for reporting this to us.  

I understand adding a linebreak (or enter) is not working properly in the repository issue tracker descriptions and comments.

I can confirm that this is a bug on Bitbucket Cloud affecting repository issue tracker descriptions and comments.  

We do have an existing bug ticket for it that can be located through this link. - <https://jira.atlassian.com/browse/BCLOUD-22992>  
You can watch and click the "This affects my team" button so that you'll be notified of any updates from our team when the bug is fixed.

As a workaround, what you can do for now is to draft your description in a text editor (with linebreaks) and paste it to your repository issue description then click save.

Apologies for the inconvenience this is causing you and your team.  
Please don't hesitate to let us know if you have any further questions that I can help with.

<br />

Regards,  
Mark C


Tags: bitbucket-cloud

cloud
Lost access to all my repos after swithing from username to email for logon
Asked by volynsm1:

Hello!

I used to login using my logon \<redacted\>. Now the system doesn't allow me to use my logon and I am using my e-mail instead (the same e-mail which was attached to my \<redacted\>) but I lost access to all my repositories from all my workspaces.

Can you please let me know how I can return access to my repos please.

Thanks,

Mike Volynski

\<redacted\>


Answers:
author: Patrik S
body: Hello [@volynsm1](/t5/user/viewprofilepage/user-id/858240) and thank you for reaching out to Community!

Checking internally for the email you shared, I see the bitbucket account associated with that email has access to multiple workspaces. Some workspaces do contain repositories, while others don't. It might be the case that you are looking at the wrong workspace.

In this case, I would suggest:

* Logging in to <https://bitbucket.org> with that email again
* Click on your **personal avatar** in the top right
* Select the **All Workspaces** option
* A list of all the workspaces to your account has access to will be shown

from that list, you can select the workspace you want, and check its repositories by clicking on the **Repositories** option in the top navigation bar.

If you have any questions, feel free to ask!

Note: I've removed your email address from the question's description to protect your privacy, as this is a public forum.

Thank you, [@volynsm1](/t5/user/viewprofilepage/user-id/858240) !

Patrik S


Tags: bitbucket-cloud

cloud
Pipeline fails - no space left on device
Asked by binternet:

When running the pipeline using atlassian/ssh-run:0.2.2 image, the following error occurs:  

+ tar -xf vendor.tar.gz  
338
tar: vendor/tecnickcom/tcpdf/fonts/cid0kr.php: Wrote only 1536 of 10240 bytes  
339
tar: vendor/tecnickcom/tcpdf/fonts/dejavusansmonob.z: Cannot write: No space left on device  
And then the pipeline fails, what could cause that?


Answers:
author: Patrik S
body: Hello [@binternet](/t5/user/viewprofilepage/user-id/2623179) and thank you for reaching out to Community!

This error message is usually returned when you have insufficient disk space in the machine where you are trying to execute that operation. In your case, it seems there's not enough space in the disk for the tar command to complete.

Could you try to free up some disk space and check if the pipeline succeeds?

If you are using runners, there's also a possibility that the runner's working directory is running out of disk space. In this case, I would suggest checking the troubleshooting steps of the following article :

* [Self-hosted runners failing with error "no space left on device"](https://confluence.atlassian.com/bbkb/self-hosted-runner-failing-with-error-no-space-left-on-device-1283492179.htm)

If you have any questions, let us know!

Thank you, [@binternet](/t5/user/viewprofilepage/user-id/2623179) !

Patrik S

comments: author: binternet
body: Hey [@Patrik S](/t5/user/viewprofilepage/user-id/4603309)   
I am using ++atlassian/ssh-run:0.2.2++ runner which is not owned by me, so how can I free the disk space on it?  

<br />


author: Patrik S
body: Hello [@binternet](/t5/user/viewprofilepage/user-id/2623179) ,

The **[atlassian/ssh-run](https://bitbucket.org/atlassian/ssh-run/src/master/)** is what we name a pipe (learn more about [pipes](https://bitbucket.org/product/features/pipelines/integrations)).

Essentially, this particular pipe will connect to an external server over SSH and run the command or script you have provided in the pipe variables. It seems like the destination server is running out of space, which is leading to the error you are receiving. Could you check the available disk space in the destination server and free up some space if possible ?

Also, it seems you are using an old version of that pipe. If you would like, you can use the latest version by changing the definition to

```
atlassian/ssh-run:0.7.1
```

Thank you, [@binternet](/t5/user/viewprofilepage/user-id/2623179) !  
Patrik S


author: binternet
body: Yaiks! my bad ?????  
I did had an issue with disk space on the remote server, issue fixed.  
Additionaly, I've upgraded to

```
atlassian/ssh-run:0.7.1
```

Thanks!!


Tags: bitbucket-cloud

cloud
How to get an year?s data of all commits and pull requests made by all users in Bitbucket.
Asked by Sravya Nalla:

Requirement : To obtain an year's data of all commits and pull requests made by all users(indian users) from every project in our Enterprise Bitbucket.

Is there any way we could do get this data using api's or code?? or any plugins for this requirement!?


Answers:
author: Ben
body: Hi Sravya,

I'll need more clarification on this one. May I know what is meant by "data"? Are you referring to stats (ie total no. of commits, how many commits each user made) or just a full list of those commits and their content? Is there anything present that is unique in say, the user's email address or some other unique aspect that defines that user as an Indian user so that it may be fed into a filter query?

I'd start by checking our /2.0/repositories API endpoint as a first step, as there are several queries you can run to pull data related to commits:

* <https://developer.atlassian.com/cloud/bitbucket/rest/api-group-commits/#api-repositories-workspace-repo-slug-commits-get>

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-server

server
Old account inaccessible
Asked by Alankar Dutta:

I had an old Bitbucket account which I cannot access. Instead, on trying to log in, it took me to the sign-up page and a new account seemed to have got created when I tried to sign in with my email alankardutta@iisc.ac.in

I have valuable codes in workspaces in the previous account which I cannot access anymore. Can you help me recover the old account?  

As this new account got created, I got an email with the following:  
One of the confirmed email addresses ([alankardutta@iisc.ac.in](mailto:alankardutta@iisc.ac.in)) associated with **Alankar Dutta** was removed because someone else verified ownership of the address on a different account.  

How to fix this and recover my previous workplaces?


Answers:
author: Ben
body: Hi Alankar,

Please refer to the below article for troubleshooting steps:

* <https://confluence.atlassian.com/bbkb/email-address-transferred-to-a-new-account-1188411865.html>

Let me know if any issues.

Cheers!

- Ben (Bitbucket Cloud Support)

comments: author: Alankar Dutta
body: Thanks for the info. This was helpful.


Tags: bitbucket-cloud

cloud
Build status keys from commit Id using Bitbucket REST API
Asked by Sebastien Ashby:

Hi,  

I wish to use the Bitbucket REST API to GET build statuses.  
To request "[get a specific build status](https://developer.atlassian.com/server/bitbucket/rest/v815/api-group-builds-and-deployments/#api-api-latest-projects-projectkey-repos-repositoryslug-commits-commitid-builds-get)" I need to provide parameters

* projectKey
* commitId
* repositorySlug
* key

My challenge is on how to get the build status "keys" associated with the "commitId".  
I am aware of the request "[get build statuses for commit](https://developer.atlassian.com/server/bitbucket/rest/v815/api-group-deprecated/#api-build-status-latest-commits-commitid-get)", but it indicates that its deprecated.  
This with the comment:

* "Deprecated in 7.14, please use the repository based builds resource instead."

I don't see any entries in the "[repository based builds resource](https://developer.atlassian.com/server/bitbucket/rest/v815/api-group-builds-and-deployments/#api-group-builds-and-deployments)" which allow me to get the build statuses for a commit.  
What am I expected to use?  
Please help...


Answers:
author: Naveen Kumar_Appfire
body: Hi [@Sebastien Ashby](/t5/user/viewprofilepage/user-id/5105778)

It is possible to get a build status commit using the [Bitbucket Command Line Interface (CLI)](https://marketplace.atlassian.com/apps/1211193/bitbucket-command-line-interface-cli?hosting=datacenter&tab=overview)

Also, please refer to this article for more info [Bitbucket CLI examples](https://appfire.atlassian.net/wiki/spaces/SCLI/pages/73371753/Examples)


Tags: bitbucket-server

rest

rest-api

server
ARM pipelines runner stops working if Docker moved to SSD
Asked by Michael Friedman:

We set up a self-hosted ARM runner for our Bitbucket Pipeline on an NVidia Jetson Xavier AGX. The runner worked well, but there wasn't much space left on the drive that Docker was on, so we installed an SSD and moved Docker's data root directory onto there. Unfortunately, that meant the Bitbucket Pipeline stopped working, with no error message given.

The attached photos show the results of running the exact same commit's Pipeline on the main Xavier drive, vs. on the SSD, using the identical runner. Both find the runner, but one just hangs up after about a minute (logs of the runner container also attached as a photo, ending with "Completing step with result Result{status=FAILED, error=None}"), the other processes as usual - also seems to divvy things up differently between the runner and build steps.

\`docker system info\` is identical for both setups, except for the "Docker Root Dir" field.


Answers:
author: Michael Friedman
body: ![docker_on_main_drive_results.png](https://community.atlassian.com/t5/image/serverpage/image-id/294236i45C23D5BD9200E98/image-size/large?v=v2&px=999 "docker_on_main_drive_results.png")![docker_on_ssd_results.png](https://community.atlassian.com/t5/image/serverpage/image-id/294237i9E50EA8034C6A44F/image-size/large?v=v2&px=999 "docker_on_ssd_results.png")![logs.png](https://community.atlassian.com/t5/image/serverpage/image-id/294235i7F1D2D42642FD967/image-size/large?v=v2&px=999 "logs.png")

comments: author: Michael Friedman
body: \^\^These are the images, forgot to press Insert on main post


author: Lars Martin Sandvik Aas
body: Hi Michael.

Did you find a solution to this?


Tags: bitbucket-cloud

cloud
Broken Pipe in own Runner with Pipe
Asked by Engin Yildirim:

I am using the following pipe at the end of my script everything until then works fine, then i am kinda stuck here for 10 mins and after that i get a broken pipe.

Afaik i registered the ssh key on the taget server and on bitbucket this runs fine, but not on my local runner. Does my local runner get all the ssh keys from bitbucket to connect correctly, or what could be the problem?

My Runner is running in a docker container on Linux.

- pipe: atlassian/sftp-deploy:0.5.12  
variables:  
USER: "USERNAME"  
SERVER: "IPADRESS"  
REMOTE_PATH: "DIRECTORY"  
LOCAL_PATH: "dist/\*"  
DELETE_FLAG: "false"  
EXTRA_ARGS: "-P PORTNUMBER"


Answers:
author: Mark C
body: Hi [@Engin Yildirim](/t5/user/viewprofilepage/user-id/5374059)  

Welcome to the community.  

To get more information from your Pipes script, you can add the variable **DEBUG: 'true'** so that you can troubleshoot it further.  

<br />

Regarding SSH key, you should be able to use SSH keys using [Linux Docker](https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/).  

Could you check if you can connect to the server via a terminal/command prompt from your local machine?  

Regards,  
Mark C


Tags: bitbucket-cloud

cloud
How we can import GCP google cloud source existing repo to my bit bucket repository
Asked by Monalisa Barik:

We have existing private Google cloud source repository and now we want to import same repository to my Bitbucket repository.

Kindly guide us how we can do the same


Answers:
author: Ben
body: Hi Monalisa,

If you'd like to import a repository from GCP, you can do so by following the steps below:

1. Create a new, empty repository on Bitbucket Cloud
2. Clone the repository that you wish to import to Bitbucket from the Google Cloud platform
3. Run the following command on your local clone of the Google Cloud repository and replace the username/workspaceID/repository name with actual values that relate to Bitbucket Cloud (without the \<\>):  
   **git remote set-url origin https://\<YourUsername\>@bitbucket.org/\<WorkspaceID\>/\<repositoryName\>.git**
4. Run git push origin on the local clone of your repository
5. The repository should then be available on Bitbucket

**NOTE:** Our repository import tool does not formally support GCP url's, however, the above process is identical to what is performed by the repository import tool. This means that only core repository content will be transferred over, any metadata such as PR's and user access settings will need to be manually created

Hope this helps.

Cheers!

- Ben (Bitbucket Cloud Support)

comments: author: Monalisa Barik
body: Thanks for providing valuable input. It helps us.


Tags: bitbucket-cloud

cloud