youngmon/atlassian-qna huggingface dataset:
How to close parent ticket automatically when all subtasks are closed using JWME ?
Asked by Mina Soultan:

I cant access parent issue through JWME post function "Transition issue" as I want want to close the parent issue when all its subtasks are closed   

<br />


Answers:
author: Walter Buggenhout
body: Hi [@Mina Soultan](/t5/user/viewprofilepage/user-id/5069109),

This is a use case documented in [this blogpost by the vendor](https://appfire.com/resources/blog/jmwe-cloud-guide-configuring-post-functions) (look for *part 3 of 3*).

Hope this helps!

comments: author: Mina Soultan
body: Thank you so much Walter


Tags: cloud

jira-service-management

jira-service-management-cloud
connected email account connectivity goes down
Asked by Fadi CHEBLI:

connected email account connectivity goes down with the admins un-aware of it. how to be notified as admins that an email connected account is no longer reacheable , or having troubles ... ?


Answers:
author: Brant Schroeder
body: [@Fadi CHEBLI](/t5/user/viewprofilepage/user-id/5467235) welcome to the Atlassian community

I am assuming that you are using a custom email account. I am not aware of anything that will let you know in JSM if it is down other than the logs. You could go the other way and if mail has not been popped you can send a message from the email account.


Tags: cloud

jira-service-management

jira-service-management-cloud
How to Disable "More Actions" column in dashboard widgets
Asked by Chmel_ Stepan:

In the last Jira cloud update new system column appeared in dashboard widgets named "More actions". Is there a way how to disable/remove this column?

Jira version:

```
{"baseUrl":"https://atajira.atlassian.net","displayUrl":"https://atajira.atlassian.net","displayUrlServicedeskHelpCenter":"https://atajira.atlassian.net","version":"1001.0.0-SNAPSHOT","versionNumbers":[1001,0,0],"deploymentType":"Cloud","buildNumber":100248,"buildDate":"2024-03-29T13:20:06.000+0100","serverTime":"2024-04-02T13:51:45.164+0200"}
```

![Screenshot 2024-04-02 134902.png](https://community.atlassian.com/t5/image/serverpage/image-id/315740iE8089CBB91A0DEBD/image-size/large?v=v2&px=999 "Screenshot 2024-04-02 134902.png")


Answers:
author: Rebekka Heilmann _viadee_
body: Hi [@Chmel_ Stepan](/t5/user/viewprofilepage/user-id/5467190) and welcome to the Community,

interestingly, I don't get the Column name but only get the 3 dots on my test site.

![Screenshot 2024-04-02 171555.png](https://community.atlassian.com/t5/image/serverpage/image-id/315810iC1E7DD5777D5D0A1/image-size/large?v=v2&px=999 "Screenshot 2024-04-02 171555.png")

Regardless, I didn't find a way to disable that column. Atlassian has changed the Gadget to be closer to what the normal search results look like. You should find the same view (possibly different columns) when you open the Filter in the Issue search.

comments: author: Chmel_ Stepan
body: Thank you for you answer [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) !


author: Robin Surland
body: The "feature" has messed up the viewing off all my dashboards, and I don't really want stakeholders who are viewing dashboards to think they can go in and start editing the data.


Tags: cloud

jira-service-management

jira-service-management-cloud
How to link between Jira work management Task to Jira service management incident.
Asked by Rahul Ranadive:

Completed JIRA Task should transit to VnV as per the workflow. This "VnV task" need to communicate (duplicate) to VnV team by generating incident request in JIRA service management. Automation has end to end this flow in software management side but the error shows:

"No request types found for incident"

Where I went wrong? I'm new to the JIRA service management.

Thanks in advance !!


Answers:
author: John Funk
body: Hi Rahul,

Sorry, but this is very hard to follow. Is this an automation rule that creates and links the issues? If so, please provide a screenshot of the rule. Or is it a manual linking?


Tags: cloud

jira-service-management

jira-service-management-cloud

jira-software-development
Not allowing customera to use the portal to which they have a link and added to the jira project
Asked by Vera Valshonok:

Hi, Community!

I have a project in jira which was used actively by customers. Now we have migrated the project to the other jira site, but customers still have access and use the previous site portal because we still have a project there where they were added previously and would like to keep it there.

How can we close ability to use the portal on the original site for the customers?

Is its impossible to do, is there a way to delete customers from a project in Bulk?

Thanks in advance!


Answers:
author: Jack Brickey
body: Hi [@Vera Valshonok](/t5/user/viewprofilepage/user-id/5174542) ,

Here are some options:

* archive the project in the old instance if it is not needed
* update permission scheme - settings \> issues \> permission schemes, find your project's scheme and update the permissions to remove Service Project Customer - Portal Access from Browse. Important don't do this if the scheme is used in other projects where you wish to retain browse access.
* hide all Request types from portal
* remove customers from the project or instance. Note that there is not a quick bulk remove.

comments: author: Vera Valshonok
body: Thanks a lot for the detailed answer! If we still need this project to not be lost and exist , can we archive it and then restore when customers will be more clear that they need to use the other site (as they wont be able to u se old one)?

How long a project can stay in archive without being automatically deleted?

* hide all Request types from portal - all the request types in the project i want to lomis access to? what if we use only one request type in this project?


author: Jack Brickey
body: You can archive for as long as you want. Here are my recommendations:

* if neither Agents nor customers need access then archive.
* if agents need access but not customers BUT these customers need access to the old issues then hide the request types so that customers cannot create new issues
* if agents need access but not customers AND these customers do not need access to any other project in this instance then remove customers from the instance altogether.

in any event, if this instance should no longer be accessed now or in future you should ultimately remove customers.


author: Vera Valshonok
body: Thanks a lot! We will remove all customers from the project as they don't need access from this restricted project anymore and agents need.


Tags: cloud

jira-service-management

jira-service-management-cloud
Pull request to prod branch shows incorrect branches by default
Asked by Jim Glenn:

![Screenshot 2023-04-19 at 4.46.20 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/252823iCBC787BAA498A30C/image-size/large?v=v2&px=999 "Screenshot 2023-04-19 at 4.46.20 PM.png")Does anyone know of a way to make the pull request default to master -\> prod branches in the pull request window?

It always shows up backwards to me suggesting making a pull request from prod -\> master even though there are no changes.

I tried to submit a request to support but it didn't help. It used to work before the last changes they did the UI for pull request.


Answers:
author: Patrik S
body: Hello [@Jim Glenn](/t5/user/viewprofilepage/user-id/4340099) ,

Thank you for reaching out to Atlassian Community.

I'm afraid you are being affected by a known bug in our platform where the branches are auto-filling backward in Pull-Requests when you have the main/master branch set as "Development" and the **prod** branch set as "Production". This bug is being tracked in the following ticket :

* <https://jira.atlassian.com/browse/BCLOUD-22313>

I see you have already added your vote there and marked yourself as a watched, so you will be notified by email whenever there's any progress on that ticket. Please note that all bug fixes are implemented with [this policy](https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html) in mind. Unfortunately, we can't provide an ETA for when it will be fixed. The current workaround would be to manually select the branches during the PR creation.

Thank you, [@Jim Glenn](/t5/user/viewprofilepage/user-id/4340099) !

Patrik S


Tags: bitbucket-cloud

cloud

pull-request
The Question is I would like to get the commits and pull requests in a certain time range.
Asked by Bharath Reddy:

Hello Community,

I am on the way of creating Grafana Dashboards, I am trying to retrieve the commits for the repository only on a certain time range. May I please know if Bit Bucket cloud supports the since and until feature on the Api end points.


Answers:
author: Ben
body: Hey Bharath,

Unfortunately - only some of what you are requesting is possible within our API at present.

Our [/2.0/repositories endpoint](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-commits/#api-repositories-workspace-repo-slug-commits-get) does not support filtering by date for commits, however, you can use GIT commands to retrieve a list of commits since a certain date or before a certain date (you can add --count switch to just show the number):

```
git rev-list --all --since 2023-01-01
git rev-list --all --before 2023-01-01
```

As for [pull requests](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/#api-repositories-workspace-repo-slug-pullrequests-get), you can use filtering and sorting to pull this information - you will need to encode any query manually or using a tool to convert it to URL format, for example:

```
//This is the base query unencoded for > than a certain date and < than a certain date

https://api.bitbucket.org/2.0/repositories/{workspaceID}/{reposlug}/pullrequests?fields=values.id&q=updated_on<2023-01-01T00:00:00+00:00&state=ALL&pagelen=50

https://api.bitbucket.org/2.0/repositories/{workspaceID}/{reposlug}/pullrequests?fields=values.id&q=updated_on>2023-01-01T00:00:00+00:00&state=ALL&pagelen=50

//These are the same queries encoded in URL format

https://api.bitbucket.org/2.0/repositories/{workspaceID}/{reposlug}/pullrequests?fields=values.id&q=updated_on%3C2023-01-01T00%3A00%3A00%2B00%3A00&state=ALL&pagelen=50

https://api.bitbucket.org/2.0/repositories/{workspaceID}/{reposlug}/pullrequests?fields=values.id&q=updated_on%3D2023-01-01T00%3A00%3A00%2B00%3A00&state=ALL&pagelen=50
```

**NOTE:**You will need to remove the curly braces and replace these with actual values in your cURL command.

We have raised a feature request on your behalf to include date filtering in our commits endpoint:

* <https://jira.atlassian.com/browse/BCLOUD-22613>

Please feel free to "Watch" this request to receive updates related to it and "Vote" for it to improve its visibility with regard to customer demand, you can view our feature implementation policy below:

* <https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html>

Hope this helps.

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

cloud
Atlasian Bitbucket Server v6.10.0 To v8.9
Asked by olcay parlak:

Hello friends, We have Bitbucket Server version 6.10. Can we upgrade directly to version 8.9, or do we need to first upgrade to any intermediate versions?


Answers:
author: Fabio Racobaldo _Herzum_
body: Hi [@olcay parlak](/t5/user/viewprofilepage/user-id/5103157) and welcome,

as explained [here](https://confluence.atlassian.com/bitbucketserver/bitbucket-server-upgrade-guide-776640551.html) you can update from any previous version of Bitbucket Server (or Stash) to the latest version, as there is no required upgrade path.

Hope this helps,

Fabio


Tags: bitbucket-server

server
Need to increase webhook limit
Asked by Sprinto:

I have seen this request from other questions, and I'm working with a system that is increasing and need 200+ webhooks. Could a team member help remove the webhook limitation on my Personal workspace?

[@Syahrul](/t5/user/viewprofilepage/user-id/744536)


Answers:
author: Ben
body: G'day Sprinto!

I've just removed the soft limits for webhooks/issues/repository creation that are imposed by default to prevent abuse.

You should now be able to create the 200+ webhooks you require on your personal workspace at this point in time.

Please let me know if you encounter any issues.

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

cloud
Where IP Allowlisting is applied?
Asked by Aiden_han:

Hi, I have a question to IP Allowlisting feature on Premium Plan.(We are considering getting the Premium Plan)

Can I apply IP Allowlisting to workspaces or repos/projects?

I checked topics about IP access restriction in Bitbucket Community, but I've been so confused because the content of each answer is different.

Please tell me exactly where IP allowlisting is applied.

Thanks in advance!


Answers:
author: Fabio Racobaldo _Herzum_
body: Hi [@Aiden_han](/t5/user/viewprofilepage/user-id/5199477) ,

welcome to the Atlassian community!

Please take a look to the following article <https://support.atlassian.com/bitbucket-cloud/docs/control-access-to-your-private-content/>

For my knowledge, allowlisted IPs can be setup for instance basis and not for a specific project/repo. If you take a look to the following image, Access controls button is on the workspace settings

![image-20210511-001344.png](https://community.atlassian.com/t5/image/serverpage/image-id/145861iB149915164900632/image-size/large?v=v2&px=999 "image-20210511-001344.png")

Fabio


Tags: bitbucket-cloud

cloud
Stenciljs error end to end test
Asked by Pawan Singh:

![MicrosoftTeams-image (13).png](/t5/image/serverpage/image-id/252511i08583E1FC1664D1A/image-dimensions/409x278?v=v2 "MicrosoftTeams-image (13).png")

*** ** * ** ***

When I ran end to end unit test for stencil.js I got this error in bitbucket pipeline. Local it's working properly. Tried multiple way to fix but not able to resolve. please help.


Answers:
author: Theodora Boudale
body: Hi [@Pawan Singh](/t5/user/viewprofilepage/user-id/5192873) and welcome to the community.

Just to give you some context, Pipelines builds run in Docker containers. For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. If you use a service for a step, then a second Docker container will start for the service which will share a network adapter with your build container. The repo is cloned in the build container, and then the commands of the step's script are executed. When the step finishes these Docker containers get destroyed.

The Docker container where the build is running is a different environment than your local one. You also have a different environment if you use a different Docker image in your bitbucket-pipelines.yml file, as different images have different tools installed.

We have a guide for debugging pipelines builds locally with Docker:

* <https://confluence.atlassian.com/bbkb/debug-pipelines-locally-with-docker-1167698072.html>

I would suggest following this guide to debug your build locally and see if the issue is reproducible. When debugging locally, please make sure that you use the same Docker images as in your bitbucket-pipelines.yml file instead of the ones mentioned in the guide.

If the issue is reproducible locally, then the error is not specific to Pipelines (it may be related to the Docker image of the build container or your source code). When debugging locally, you can also run additional commands to troubleshoot this further. You could also try debugging it locally with different Docker images.

If you have any questions, please feel free to let me know.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Bitbucket Cloud connection to Jira Datacenter
Asked by Benjamin Newton:

Hello,

We're attempting to connect our JIRA Datacenter instance to our Bitbucket Cloud repository.

We've set things up following these instructions:

<https://support.atlassian.com/bitbucket-cloud/docs/connect-bitbucket-cloud-to-jira-software-server/>

However, that does not seem to allow us to link our pull requests/commits to JIRA issues, and these cloud instructions do not seem to apply to datacenter:

<https://support.atlassian.com/jira-cloud-administration/docs/connect-jira-cloud-to-bitbucket/>

Is there a way we can see our Jira datacenter issues in our bitbucket cloud repo?


Answers:
author: Theodora Boudale
body: Hi Benjamin and welcome to the community!

A common cause for this issue is permissions:
> **Project permissions required**
>
> Project users must have the 'View Development Tools' permission to see commit information in the Development panel in a Jira Software issue. A Jira Software admin can edit a project's permission schema to grant this permission. See [Managing Project Permissions](https://confluence.atlassian.com/adminjiraserver070/managing-project-permissions-749382918.html).

If these permissions are ok, we would need to review your setup to further investigate. I see that you already created a ticket with the support team, so I would suggest focusing on the ticket in order to avoid any confusion and miscommunication that may arise from troubleshooting the same issue in two different places.

Once the issue is resolved, feel free to share here the resolution for any other users that may come across your post facing the same issue.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
Reduced Repo Size, Local repo size <500 MB but on Bitbucket it shows 3.2 GB
Asked by santpal:

I tried to clean up my repository and reduce the size since I was getting 2GB warning. I deleted a big size folder from history and repository. My local repository size is now 439M but on Bitbucket cloud the repo size increased to \~3.2 GB. I tried git gc and it didn't help. Any ideas how to reduce the size of repository on bitbucket.


Answers:
author: Theodora Boudale
body: Hi [@santpal](/t5/user/viewprofilepage/user-id/5198564) and welcome to the community!

If you rewrite history and push to the remote, it is expected that its size will go up, because the remote repo will contain both old references (prior to history rewrite) and new ones (after history rewrite). A git gc is needed on the remote repo to remove any old references. While end users can run a git gc on their local repo, it is not possible for them to trigger a git gc on the remote repo.

I checked the repos your account has access to, I found the one with a size of 3.2 GB and I ran a git gc on it. Its size has been reduced, please feel free to let me know if it looks ok on your end.

We have a feature request for allowing users to trigger a git gc on their remote repos:

* <https://jira.atlassian.com/browse/BCLOUD-11593>

In the meantime, if you ever rewrite history again and would like a git gc for your remote repo, you can create a question in community and a member of the support team can do it.

Kind regards,  
Theodora

comments: author: santpal
body: Yes, I see the size is reduced. Thanks got it


author: Theodora Boudale
body: Thank you for the update and you are very welcome!

Please feel free to reach out if you ever need anything else.

Kind regards,  
Theodora


author: Fabio Racobaldo _Herzum_
body: Hi [@santpal](/t5/user/viewprofilepage/user-id/5198564) and welcome,

probably you local repo has not all the history. Btw, in order to reduce repo size, please take a look to the following article <https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/>

Hope this helps,

Fabio

comments: author: santpal
body: Hi Fabio,

I followed the link above. The issue is that I removed file/folders from repo to reduce the size of the repo - The size reduced on the local repo but on bitbucket the size increased to even more than before giving me 2GB warning again. I don't see any dangling commit either. Rewind history will lead me to files and folders that I didn't want in the first place.


Tags: bitbucket-cloud

cloud
bitbucket-pipe-relase 5.3.1 fails to push back to repo
Asked by Christof Koegler _Gaims GmbH_:

I just updated a pipeline to use the latest version 5.3.1 of the \`bitbucket-pipe-release\` pipe. However the pipe fails to push back to the repo with the error message:

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/252408i48A55FF90F0B165F/image-size/large?v=v2&px=999 "image.png")  
I have not set up an SSH key, but pushing back to the repo has not previously required that (the pipeline is unchanged apart from updating the \`bitbucket-pipe-release\` version).  
Has this been changed?


Answers:
author: Theodora Boudale
body: Hi Christof,

It is not necessary to set up SSH keys; if you don't configure SSH keys, the http proxy and http origin will be used to push. I reached out to the development team regarding this error, I will let you know as soon as I have an update.

Kind regards,  
Theodora

comments: author: Daniel Hilgarth
body: Any update on this?


author: Igor Stoyanov
body: [@Christof Koegler _Gaims GmbH_](/t5/user/viewprofilepage/user-id/5011301), [@Daniel Hilgarth](/t5/user/viewprofilepage/user-id/564881) hi.  
A new version of the pipe released, that should fix this issue:  
<https://bitbucket.org/atlassian/bitbucket-pipe-release/src/5.3.2/>  

Waiting for your feedback.  

Regards, Igor


author: Christof Koegler _Gaims GmbH_
body: Hello [@Igor Stoyanov](/t5/user/viewprofilepage/user-id/4550492) [@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086) the update has resolved the issue. Thank you!

Best regards,

Chris


author: Theodora Boudale
body: That's good to hear Christof, thank you for the update!


Tags: bitbucket-cloud

cloud