youngmon/atlassian-qna huggingface dataset:
Bamboo Update to 6.2.5
Asked by Matthew Lyons:

I'm attempting to upgrade our bamboo to version 6.2.5, but now it won't launch:

Bamboo bootstrap failed: Your build of Bamboo (5920) is too old to work with the data in your Bamboo home directory (C:\\bamboo\\bamboo-home), which comes from build number 51211

I've googled the problem but I can't find a solution to work for me?


Answers:
author: Matthew Lyons
body: error


author: Alexey Chystoprudov
body: Message says you're trying to run Bamboo 5.9 at Bamboo 5.12 home. Please check if you run correct version of Bamboo during upgrade

comments: author: Matthew Lyons
body: For upgrade I ran atlassian-bamboo-6.2.5-windows-x64.exe


author: Matthew Lyons
body: Can we talk on the phone or skype?

I need to get this running this afternoon and I'm not very familiar with how bamboo works.


author: Alexey Chystoprudov
body: Sorry, [@Matthew Lyons](/t5/user/viewprofilepage/user-id/1188921), but phone and skype calls are for Primer Support clients only.

How does it work if you try to use empty Bamboo home folder?
Application links between Bitbucket and Bamboo
Asked by Lasse Langhorn:

After connecting a Bamboo instance (version 6.2.5) and a Bitbucket instance (version 5.5.0) via Application links, I receive an error  
in the Bitbucket UI and an error is shown in the log.

```
Caused by: com.atlassian.sal.api.net.ResponseStatusException: Unexpected status: 403
 at com.atlassian.applinks.internal.common.net.ResponsePreconditions.checkStatus(ResponsePreconditions.java:28)
 at com.atlassian.applinks.internal.common.net.ResponsePreconditions.checkStatus(ResponsePreconditions.java:17)
 at com.atlassian.applinks.internal.common.net.ResponsePreconditions.checkStatusOk(ResponsePreconditions.java:37)
 at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$2.handle(AppLinksManifestDownloader.java:177)
 at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:104)
 at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.doDownload(AppLinksManifestDownloader.java:165)
 ... 49 common frames omitted
```

The error only occurs on Bitbucket not on Bamboo. I can curl from the Bitbucket server to the Bamboo server and get a response from the manifest REST endpoint, so the network connection seems fine to me.  
So the instances can see each other, but for some reason Bitbucket responds with an error in the UI. More specific the error in Bitbucket is something like this:

```
Unexpected response
We received an unexpected response from Atlassian Bamboo. If the remote application is behind a proxy, check that the application is operational. Troubleshoot this for other possible causes.
403: Forbidden
To see the full response content look at your application logs
```

The Bitbucket instance does not have http.nonProxyHosts parameter set.

Have anyone experienced something like this before?

Thanks.


Answers:
author: Danyal Iqbal
body: ```
Unexpected status: 403
```

means that the resource is forbidden.

Bitbucket user does not have rights for bamboo.

The 403 error is essentially saying "Go away and don't come back here." You can check these as well but I am sure, you need more rights to get rid of this exception :)

* Check the URL. Must be a valid page, not a directory on the server.
* Make sure the user has the permissions to access the resource.
* Clean cache.
* check proxy settings

comments: author: Lasse Langhorn
body: Hi [@Danyal Iqbal](/t5/user/viewprofilepage/user-id/430572),

Thanks for the quick response.

It looks like a proxy setting issue.

Best regards

Lasse


author: Lasse Langhorn
body: When you have several Atlassian apps communicating with each other, check the proxy settings.

In my case I did not had the correct proxy settings for the Bitbucket app applied. Check this link: <https://confluence.atlassian.com/bitbucketserverkb/how-to-configure-an-outbound-http-and-https-proxy-for-bitbucket-server-779171680.html#HowtoconfigureanoutboundHTTPandHTTPSproxyforBitbucketServer-ApplicationLinks>.

My loadbalancer caused the problems. After applying the

    -Dhttp.nonProxyHosts

parameter things start to work
Bamboo Specs deployment project still configurable via ui?
Asked by Lars Niestrad:

Bamboo plans managed by bamboo specs are not configurable via the ui. That is a good thing because it prevents that the configuration stored in the specs repository and the one in the ui will drift apart.

However, I introduced bamboo specs for one of our deployment projects, too and there seems to be no functionality to lock the deployment project configuration via ui. I can still modify everything without the use of my specs repository.

Now my question is, whether this is intended or not. I think it would be very useful if I could lock my deployment project the same way, the build plan will be locked after detecting the corresponding specs repository. Is this a missing feature or did I miss something?

Kind regards

Lars


Answers:
author: Alexey Chystoprudov
body: It's not implemented yet. Bamboo team has plans to resolve several UI-related issues for deployments managed by Bamboo Specs. It will be addressed in future releases

comments: author: Lars Niestrad
body: Okay. Is there a Jira issue related to this topic in the public Bamboo Jira so I can track the progress/ potential release version and so on?


author: Alexey Chystoprudov
body: <https://jira.atlassian.com/browse/BAM-19694>


author: Lars Niestrad
body: Thanks!
Deployment in multiple servers
Asked by loganathan:

How to deploy an application in multiple servers using one deployment plan?


Answers:
author: Gonchik Tsymzhitov
body: Hi !

In fact, for deploy on many servers, just create multiple environents.

Hence you can deploy on multiple servers.

Reference:

<https://confluence.atlassian.com/bamboo/creating-a-deployment-environment-338363440.html>

Hope it helps,

Cheers,

Gonchik Tsymzhitov

comments: author: loganathan
body: Hi ,

Thanks for your reply

please find the needs below

In production environment, we have multiple servers for different regions. So, how to deploy on multiple servers in a single environment?


author: Gonchik Tsymzhitov
body: Hi!

Let's define the more agents

<https://confluence.atlassian.com/bamboo/agents-for-deployment-environments-342754133.html>

Cheers,

Gonchik Tsymzhitov
Bamboo cloud build using REST API
Asked by Deepak:

Hi,

I am trying to invoke Bamboo REST API from Bit Bucket using plugin "Pull Request Notifier" for a pull request raised. I have invoked the URL as mentioned below and passed the pull request related parameters. But since my build plan has a task to fetch the code from a particular repository, pull request parameters passed here are being ignored and predefined repository is being fetched. Is there any way that my build plan merges the code based on passed parameters and run the build on top of that? How should my build plan look like to fetch the repository using these parameters?

I am aware that Bamboo 6 has a new feature for pull requests but our organizations current version is 5.6.2.

I have tried to implement this based on the suggestions given in the URL below

<https://community.atlassian.com/t5/Bamboo-questions/Building-Pull-Requests-from-Stash-on-Bamboo/qaq-p/77703>

URL Used:

https://\<My Bamboo Host Name\>/build/admin/triggerManualBuild.action?buildKey=\<Plan Name and Key\>\&bamboo.PULL_REQUEST_ID=${PULL_REQUEST_ID}\&bamboo.PULL_REQUEST_TO_SSH_CLONE_URL=${PULL_REQUEST_TO_SSH_CLONE_URL}\&bamboo.PULL_REQUEST_TO_REPO_NAME=${PULL_REQUEST_TO_REPO_NAME}\&bamboo.PULL_REQUEST_TO_BRANCH=${PULL_REQUEST_TO_BRANCH}\&bamboo.PULL_REQUEST_TO_REPO_PROJECT_KEY=${PULL_REQUEST_TO_REPO_PROJECT_KEY}\&bamboo.PULL_REQUEST_URL=${PULL_REQUEST_URL}\&bamboo.PULL_REQUEST_VERSION=${PULL_REQUEST_VERSION}\&bamboo.REPOSITORYSLUG=${PULL_REQUEST_AUTHOR_SLUG}\&os_authType=basic\&executeAllStages=true


Answers:
author: Gonchik Tsymzhitov
body: Hi!

on 6.10.2 it works well.

Have you checked on latest version ?


Tags: build

continuous-delivery

pull-request

rest-api
Run npm install post deployment
Asked by rob williams:

We have a .NET/Angular 4 project that builds and deploys from BitBucket to our AWS IIs instance.

We don't want to track the node_modules folder and push them to BitBucket or from the Bamboo build instance to the deployment server for obvious reasons.

What we'd like to do is run "npm install" post deployment on the webserver, and let npm do it's package managing thing, vs. pushing the node_modules folder from BitBucket to the Bamboo build instance to the webserver.

Is this possible?


Answers:
author: Alexey Chystoprudov
body: Use SSH task to run 'npm install' command as part of your deployment steps

comments: author: sisir
body: [@Alexey Chystoprudov](/t5/user/viewprofilepage/user-id/781646)Could you add more information on this. I also need to do the same!


Tags: npm
How to specify change detection regex per plan for a bitbucket linked repository
Asked by Lee Higgitt:

We have a BitBucket and a Bamboo server.

One of our BitBucket repos is set up as a "Linked Respoitory" and we have multiple plans for that one repo.

I'm attempting to specify a different change detection regex patter for one plan to another.

When I go to configure the plan \> Repositories \> \<my repository\>

All of the options are grayed out and I get the message "This is a linked repository and is accessible for all build plans in Bamboo. Go to linked repositories to edit its details"

I'm able to configure the file pattern for the Linked Repository but not on a plan per plan basis.

It's important that we have this functionality as I don't want all of my plans building every time I commit.

Can anyone help?

Lee


Answers:
author: Marcin Gardias
body: > I'm able to configure the file pattern for the Linked Repository but not on a plan per plan basis.

You can define repository in the plan itself rather than using Linked Repository. That is the only way to accomplish this as far as I can tell.

There is feature request to allow overriding of certain settings of Linked Repos at the plan level: <https://jira.atlassian.com/browse/BAM-18090>. Please place your vote, as it helps us decide which items we should work on next.
Bamboo agents version
Asked by Marina Volkova:

Hi!

We think that our bamboo agents does not updates

Where can i find agent version?


Answers:
author: Marcin Gardias
body: I think the best way is to check content of *classpath* directory in your agents' home directory.

It should look something like this, the exact list depends on the version, but the versions of the jars should match\* the version of your Bamboo server. You also should not see any duplicates (same jar in different versions)

\*) There are exceptions like dotnet plugin for instance, but you get the point.

```
ls? | grep "atlassian-bamboo-*"
atlassian-bamboo-agent-bootstrap-5.10.2.jar
atlassian-bamboo-agent-core-5.10.2.jar
atlassian-bamboo-agent-elastic-5.10.2.jar
atlassian-bamboo-agent-elastic-server-5.10.2.jar
atlassian-bamboo-agent-elastic-shared-5.10.2.jar
atlassian-bamboo-agent-local-5.10.2.jar
atlassian-bamboo-agent-remote-5.10.2.jar
atlassian-bamboo-api-5.10.2.jar
atlassian-bamboo-api-agent-bootstrap-5.10.2.jar
atlassian-bamboo-core-5.10.2.jar
atlassian-bamboo-core-agent-bootstrap-5.10.2.jar
atlassian-bamboo-deployments-5.10.2.jar
atlassian-bamboo-deployments-api-5.10.2.jar
atlassian-bamboo-language-5.10.2.jar
atlassian-bamboo-license-5.10.2.jar
atlassian-bamboo-maven-embedder-5.10.2.jar
atlassian-bamboo-plugin-ant-5.10.2.jar
atlassian-bamboo-plugin-dotnet-5.10.1.jar
atlassian-bamboo-plugin-fisheyecommitviewer-5.10.2.jar
atlassian-bamboo-plugin-grails-5.10.2.jar
atlassian-bamboo-plugin-labeller-5.10.2.jar
atlassian-bamboo-plugin-php-5.10.2.jar
atlassian-bamboo-plugin-scripttask-5.10.2.jar
atlassian-bamboo-plugin-ssh-5.10.2.jar
atlassian-bamboo-plugin-stashcommitviewer-5.10.2.jar
atlassian-bamboo-plugin-triggercondition-5.10.2.jar
atlassian-bamboo-plugin-vcs-5.10.2.jar
atlassian-bamboo-plugin-vcsversion-5.10.2.jar
atlassian-bamboo-utils-5.10.2.jar
atlassian-bamboo-web-5.10.2.jar
atlassian-bamboo-xml-utils-5.10.2.jar
```

You can also check the agent logs; if agent updates correctly you should see sth. like that:

```
[AgentContext] Important agent classes have been updated, the agent will now terminate to pick up the latest changes.
....
[ClasspathBuilder] Server publishes 341 files, we need to download 341
```

\*

comments: author: Marcin Gardias
body: One thing you can try is to force restart of an agent and see if it helps.
Option to change comment type per bulk?
Asked by Roland Siegel:

Hi,

we are moving our customer service projects form Jira Software Server (software project) to Jira Service Management Cloud and now ran into the problem that we have to migrate the internal comments (via Addon "Comment Secuity") from the customer projects to JSM Cloud as "internal note".

Is there any migration path available/known? Is it possible to change the comment type of comments of JSM tickes in bulk?

Best Regards,  
Roland Siegel


Answers:
author: Roland Siegel
body: No migration needed.

I just found out:

The secured comments are migrated correct and when the affected issues are moved from JSW to JSM the role restriction of comments is kept although you can't set such a restriction by hand in JSM.

![Screenshot - 19.03.2024 , 11_47_41.png](https://community.atlassian.com/t5/image/serverpage/image-id/312980i49CBFF2C071070DE/image-size/large?v=v2&px=999 "Screenshot - 19.03.2024 , 11_47_41.png")

Great! :)


author: Walter Buggenhout
body: Hi [@Roland Siegel](/t5/user/viewprofilepage/user-id/1559186),

This is not possible in native Jira. There was a feature request, but it was closed as won't fix: [JRACLOUD-31324](https://jira.atlassian.com/browse/JRACLOUD-31324).

An app vendor mentioned a possible workaround in the comments on that ticket with a marketplace app that you could have a look at.

Hope this helps!

comments: author: Roland Siegel
body: Hi [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225)

thanks for your answer.

It seems that this option is only available for Jira Server and not for JSM Cloud, right?

Best Regards,  
Roland


Tags: cloud

jira-service-management

jira-service-management-cloud
How can we copy all the custom fields and schemes from one Jira org to another
Asked by Nijas Rawther:

How can we copy all the custom fields and schemes from one Jira org to another?  

Do we have an API for this ? Or in the absence of an endpoint, are there other performant ways to achieve this ?


Answers:
author: John Funk
body: Hi Nijas,

You can do that with a Marketplace app called Revyz Configuration Manager for Jira (full transparency I am an advisor for the app). You can do a free trial and give it a test.


author: Luka Hummel - codefortynine
body: Hi [@Nijas Rawther](/t5/user/viewprofilepage/user-id/5079290)

We have just released an update for [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2635859) that enables you to clone whole projects, including their configuration for different schemes, between different Jira Cloud instances.

![Screenshot 2024-04-10 at 14.30.44.png](https://documentation.codefortynine.com/__attachments/1504018433/Screenshot%202024-04-10%20at%2014.30.44.png?inst-v=340f2aa9-b19c-4086-9230-dcc24690836c)

You can read more on this new feature [here](https://documentation.codefortynine.com/deep-clone-for-jira/clone-a-project-to-another-instance?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2635859).


author: Marc - Devoteam
body: Hi [@Nijas Rawther](/t5/user/viewprofilepage/user-id/5079290)

I suspect you mean a complete other Jira instance where you want the same options?

The only way is to make a backup of the instance and import that in the other Cloud instance. (This will overwrite all existing information in that instance)

There is no API way for this.


Tags: cloud

custom-field

jira-service-management

jira-service-management-cloud

scheme
Not Recieving Verification Emails
Asked by Martin Anderson:

There are two atlassian users in my organisation who are not recieving verification emails from atlassian, but this is not the case for some accounts within the same organisation. I have only tried deactivating their accounts and reactivating and that doesn't help.

I wish my problem can be attended to and I can provide the email addresses upon request.

Thank you.


Answers:
author: Nikola Perisic
body: Hello [@Martin Anderson](/t5/user/viewprofilepage/user-id/5259619) , if you have your personal settings correct where the checkboxes are ticked for receiving the email when you are the watcher of the issue, report,etc. in that case Atlassian has supressed your email. This is mostly done to prevent spam emails. To solve this, raise a support ticket for Atlassian asking them to remove your email address from the supression list.

comments: author: Martin Anderson
body: Hello [@Nikola Perisic](/t5/user/viewprofilepage/user-id/5166624) in attempting to raise a support ticket for the problem, it led me here to the Atlassian Community portal. Could you assist with the appropriate link?


author: Nikola Perisic
body: Sure, here it is [@Martin Anderson](/t5/user/viewprofilepage/user-id/5259619) : <https://support.atlassian.com/contact/?postauth=true#/>


author: Dexter de Vera
body: Is this in sync in AD? make sure that there using the correct email.


Tags: cloud

jira-service-management

jira-service-management-cloud
Assets automation to send e-mails notifications
Asked by Valerie Blondel:

Hi there !

I am considering using assets to manage our licences inventory. I am trying to set up a notification, using automation, to send an e-mail if a licence is about to expire and need renewal.

Here is my current POC:

Scheme = Licences Management

Object type = Licences

Attribute = Expiry date (the filter "Expiry date" \<30d works perfectly fine".

![Asset 1.png](https://community.atlassian.com/t5/image/serverpage/image-id/311285iD62A2849CAD46705/image-dimensions/423x371?v=v2 "Asset 1.png")

In my automation :

![Rule details.png](https://community.atlassian.com/t5/image/serverpage/image-id/311290i1726C5AE0FCADE33/image-dimensions/284x463?v=v2 "Rule details.png")![Rule.png](https://community.atlassian.com/t5/image/serverpage/image-id/311295i0BE337F08103C64C/image-size/large?v=v2&px=999 "Rule.png")

Although the AQL is validated, audit logs shows "no object found".

![Audit log.png](https://community.atlassian.com/t5/image/serverpage/image-id/311296iB53EC777C26D3B2A/image-size/large?v=v2&px=999 "Audit log.png")

I am surely missing something, but cannot find what. Anyone there who might help ?

Last but not least, I read that I cannot use a "look up object" if more than 100 objects ? This might be an issue to me too. Any workaround ?

Thanks so much for your help !

Val?rie


Answers:
author: Tammy West
body: I had the same issue and I found that in order to return the child objects under an Abstract Object, your Lookup needs to follow this syntax...

objectType in objectTypeAndChildren(Licenses)

Hope this saves someone else the amount of searching it took me to find it.

\~Tammy


author: Adrian Kausel
body: Hello Valerie!

I checked your configuration and everything's in the right direction, I did some tests on my end replicating your setup and it worked (The email with the soon-expiring license gets fired properly).

The only difference in my query was that I'm not using the parenthesis, but that should not impact the query anyway (my query: objectType = Licenses AND "End of life" \> 25d)

After coming back to your report I noticed something that could be the issue here:

- In your first screenshot you show the query inside the **Licenses** object type, and as possible to see you are retrieving properly the expiring licences using: "Expiry date" \> 30d

- On the other hand in your automation rule you are invoking the Expiry date attribute using the query: "Expiry Date" \> 30d, which is different because you are typing Date with a capital D, this will break your call for the object as the attribute is called "**Expiry date** " and not "**Expiry Date**"

Hope this resolves your issue!

Adrian


Tags: cloud

jira-service-management

jira-service-management-cloud
JSM SLA reset/recalculate when field changed
Asked by Albert Manuel:

Hello,

We have an SLA where:

* It starts when an issue is created.
* It's stopping when a resolution is set.

The goals are a bit different:

* If field Type = Web the goal will be 1h
* If field Type = Internal the goal will be 2h

Now everything works.

BUT

Some ppl create the ticket with the type "Web," and the SLA starts with 1h, but the support team decides that the ticket should be, in fact, "Internal." They change the option of the field into the internal - at that point, we expect the SLA to "reset" or something so that the SLA will be 2h - this doesn't happen - it this possible somehow?

Thanks.


Answers:
author: Vitaly_Berezovsky_SaaSJet
body: Hi

You can install an add-on [SLA Time and Report](https://marketplace.atlassian.com/apps/1220741/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_JSM-SLA-reset-recalculate-when-field-changed_20240312) from the Atlassian Marketplace.

This add-on has a reset SLA feature: In the configuration menu, you can select the condition for SLA Reset.

This option allows you to configure conditions when the SLA timer resets every time a specific condition is met and starts running again only when the Issue is on the Start condition.

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

Here, you can select a necessary condition from the list, except the ones you have added to the Start/Pause/Stop conditions. When you select this condition, the timer stops ticking for the particular Issue when the condition is met and starts ticking again after meeting the Start condition.

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

The list of the reset conditions depends on your project settings but can include only default Jira fields, such as:

* Assignee
* Comment from
* Issue Type
* Labels
* Priority
* Reporter Status

The application has a [30-day trial period](https://marketplace.atlassian.com/apps/1220741/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_JSM-SLA-reset-recalculate-when-field-changed_20240312) and is free for small teams (up to 10 users), so you can check how well it suits you. My team developed it, so our support can help you with the settings.


author: Dirk Ronsmans
body: Hi [@Albert Manuel](/t5/user/viewprofilepage/user-id/1194936) ,

As long as your SLA is not yet Stopped it should re-calculate to your new goal.

Once stopped it will of course ++not++ recalculate so you cannot "fix" breached SLA's :)

Are you changing the Type field while it is still ongoing or after the Resoltion has been set?

comments: author: Albert Manuel
body: Hi [@Dirk Ronsmans](/t5/user/viewprofilepage/user-id/124602) this happens before the resolution is set..but somehow the new goal is not applied to the tickets and i was expecting to happen...


author: Dirk Ronsmans
body: Could you share screenshots of your SLA configuration? Details matter :)


Tags: data-center

jira-service-management

jira-service-management-data-center

sla