youngmon/atlassian-qna huggingface dataset:
Outgoing Automation Rule
Asked by justyn.rodriguez:

I'm running an Opsgenie integration with a JIRA service project, but the Outgoing Automation rule that sends updates back to JIRA ("If alert is closed in Opsgenie, set request status to Done in Jira service management cloud") is not working, what could I be missing?


Answers:
author: John M
body: Hi [@justyn.rodriguez](/t5/user/viewprofilepage/user-id/3900080) ,

If the connection is working and other actions are being successfully executed, one thing to look at would be to make sure that the Jira issue is able to move from the status it's currently in, to the 'Done' status.

If you check the activity log on the alert that was closed, there should be a log showing the attempt to update the Jira status coming from Opsgenie, and if it was not successful, it should then log the error as well.


Tags: cloud
Possible Enhancement Request for notifications
Asked by William Butt:

Hello,

I'm not sure if this is the correct venue for this however, I'm posting it regardless in the hopes that someone from the atlassian team could actually process it.

I would like to have an ER created that allows you to send emails x number of days before the action of 'schedule starts'.

Currently, you can only set it to 1 day before it starts, I would like to have the choice of choosing the days... such as 3-4 days before...

![Opsgenie nofication for start time action.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/238402iC220B64641F0110D/image-size/large?v=v2&px=999 "Opsgenie nofication for start time action.jpg")


Answers:
author: Nick H
body: Hi [@William Butt](/t5/user/viewprofilepage/user-id/4345528) ,

I believe there are already a few similar feature requests for this functionality you can follow, watch and vote for here:

<https://jira.atlassian.com/browse/OPSGENIE-315>

<https://jira.atlassian.com/browse/OPSGENIE-701>

comments: author: William Butt
body: Thanks Nick! I have followed both of these.
Opsgenie Zendesk Integration add entry
Asked by Alex Thornhill:

I've setup our Zendesk to create an Incident and Alert in Opsgenie from a new Ticket in Zendesk however I cannot see how I can get any new comments from the Zendesk ticket to flow into the Opsgenie Incident.

Ideally I'd be looking to get the comment from Zendesk ticket added to either the Latest_comment field on the Opsgenie Incident or the Add Entry field. The support page (<https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-zendesk/>) states this: For example, add a note to Opsgenie alert/incident, when a public reply is added to the ticket in Zendesk. In order to do this, define "If a public reply is added to the ticket in Zendesk, a note is added to the alert in Opsgenie". mapping in "Zendesk -\> Opsgenie" Update Section.

However when I look at the integration on Opsgenie there is no option from Zendesk to Opsgenie on the opsgenie side to add a note. There is only an option for a Zendesk Ticket when internal note added to reopen/close/resolve the opsgenie ticket.

I did see the option on the Alert for this however i'm specifically looking for this to be done on the Incident.


Answers:
author: Shashwat Khare
body: Hi [@Alex Thornhill](/t5/user/viewprofilepage/user-id/5138240) ,  

Please note that for the Zendesk Opsgenie integration, we have the functionality of adding internal notes/ public replies from Zendesk tickets to Opsgenie Alerts.  

However, for Incident Action Mapping, we currently offer only Incident state-based Incident actions such as "Resolved/Reopened/Closed".  

I have raised a Feature Request for this functionality to be available for Incidents as well and would request you to please follow the below ticket for further updates on this:  
<https://jira.atlassian.com/browse/OPSGENIE-1253>  

Have a great day ahead!   

Best,  
Shashwat


Tags: cloud

zendesk
Notifications going to wrong email address
Asked by John Alan:

I have two email addresses in my OpsG profile. One is my normal email address, one is a Slack email integration address. This address is ONLY selected for \`Schedule Start\` and nothing else.

My issue is that every notification for Services I am watching are getting sent to this email address along with my regular one.

Reviewing my Notifications shows "All Alerts" only going to my normal email address.


Answers:
author: Mona Singh
body: Hi John,

This is Mona here, happy to help :)

I understand that you're receiving Service Subscription Notification on both the emails configured under your Email contact method.

To answer your question, this is expected behavior as Individual subscribers receive an email notification on the email contact methods set within their User Profile. Please note that stakeholder notifications can only be received via email and push notifications.

**You can refer to the below doc to get more information on Stakeholder Notifications:**   
<https://support.atlassian.com/opsgenie/docs/get-started-with-opsgenie-as-a-stakeholder/>

Therefore, for service subscription notifications you should be receiving emails on both the addresses and also push notifications (if configured and the app installed)

Hope this helps. Please let us know if you have any follow-up questions and I'll be happy to answer them for you.

Thanks,  
Mona

comments: author: John Alan
body: Hey Mona, thanks for responding. My issue is that - no matter how I sent the two email addresses for alerts - they both get the alerts.

Address #1 - for all alerts/incidents excepting watched services.

Address #2 - ONLY for notification of on-call starting, nothing else.

And yet... when an alert for a watched service comes in Address #2 gets notified.


author: Mona Singh
body: Hi John,  

Thanks for your reply. Just to reconfirm my understanding, do you mean to say, when an alert or incident is created for watched services, you're receiving subscription notifications on both Address 1 and Address 2, when only 1 was added to receive Stakeholder Notifications?  

If the above-mentioned is the case then its intended behavior as service subscription notifications are sent to both the email addresses that are configured under the email contact methods set within the User Profile.  

So, let's say you have configured Addresses 1 \& 2 under your user profile and subscribed to a service in Opsgenie. Then any new alert/incident notification created via the watched service will be sent to both email addresses 1 \& 2.  

Hope it helps :) In case you have any further queries, please feel free to reach out to us by creating a ticket in this [link](https://support.atlassian.com/) and we'll take it from there :)  

Thanks!  
Mona
Revert from Jira remote user directory to local user directory for Bamboo
Asked by Kevin Huang:

Our Jira and Confluence have been migrated into Cloud. Next we would like to shut down on-prem Jira server. But on-prem Bamboo and Bitbucket are still using it for user auth.  

Bitbucket supports both local user directory and remote Jira user directory at the same time, so using local user directory for Bitbucket is not a problem for us.  

But Bamboo is quite different. We can only have one user repository at a time, either local user mode or remote user mode. I have tried to revert the user repository from Jira remote users to local users in Bamboo, but I still couldn't see the button for me to create any new local user or group.   

From the article <https://confluence.atlassian.com/bamboo0602/integrating-bamboo-with-ldap-938867314.html> , it says:  

*Please note that once LDAP has been enabled, reverting back to local user management is not possible.*

Even though we are using Jira based user directory, not using LDAP, are we still hitting the same limitations, i.e, not possible to revert back to local user management?

Or is it because of our Bamboo version 6.2.5 is too old and it lacks this functionality? Does latest Bamboo version 8.2 support user directory reverting from remote Jira user to Bamboo local user directory?   


Answers:
author: Kevin Huang
body: It turns out there is an option that we need to change from **true** to **false** in the file \<BAMBOO-INSTALL-HOME\>/xml-data/configuration/administration.xml :  

*\<enableExternalUserManagement\>false\</enableExternalUserManagement\>*   

After above change and restarting the service, we are able to create/delete local Bamboo users now.   

In summary to revert from Jira remote user directory to local user directory for Bamboo, we need:  

1) In Bamboo administration, under User repositories section, switch from **Users and groups from JIRA or Crowd** to **Local users and groups**

2)change the option from **true** to **false** in the file \<BAMBOO-INSTALL-HOME\>/xml-data/configuration/administration.xml :  

*\<enableExternalUserManagement\>false\</enableExternalUserManagement\>*

Restart the service then Bamboo is switched from Jira user directory to Bamboo local user directory.
How to change configuration using branches in yaml specs
Asked by Valerii:

Hi Team,

I want to change some parameters in my bamboo plan using branches.

For example:

I want to create Bamboo plan with different branches and each branch should have different job or task.

Is it possible to override some parameters using one yaml file configuration?


Answers:
author: Eduardo Alvarenga
body: Hello [@Valerii](/t5/user/viewprofilepage/user-id/4984397) , Welcome to **Atlassian Community!**

If you are using Bitbucket Server along with Bamboo, you can benefit from **Enhanced Plan Branches**:

* [Enhanced plan branch configuration](https://confluence.atlassian.com/bamboo/enhanced-plan-branch-configuration-1018767259.html)

Cheers,

Eduardo Alvarenga  
Atlassian Support APAC

comments: author: Valerii
body: Hi Eduardo Alvarenga,

Thank you for your response. So is it necessary to have new branch on git for new configuration BP?


author: Eduardo Alvarenga
body: Hello [@Valerii](/t5/user/viewprofilepage/user-id/4984397)

**Yes**. Enhanced plan branches are linked to your Bitbucket repository branches.

Alternatively, if you don't want to use Git branches, you can have:

* **A single Bitbucket repository** with your Bamboo specs code that will contain all your individual, independent Plans and their individual settings. Once Bamboo scans that repository, it will take action and apply the changes to every Plan it has a reference. Then, it is just a matter of creating multiple Plans and referencing your common code repository as a secondary repository for the code checkout tasks
* **Multiple Bitbucket repositories** with individual Bamboo specs code that will only contain the details for that specific plan. Each Java Specs or YAML Specs code will need to be put on a different repository. Your common code repository can be added as a second repository to each Plan and be used for the different tasks

Choosing the best strategy will vary according to your development teams and if they agree to share or if they prefer having independent Bamboo specs structures.

Eduardo Alvarenga  
Atlassian Support APAC


author: Valerii
body: Okay, so for example, here is my yaml spec configuration file:

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

In a "JIRA-custom-integration" bamboo branch I want to override only one parameter from Unit tests stage

requirements: NewGoodDocker

Everything else should be the same as in a master (default) branch.

How can I do it?


Tags: yaml
Atlassian Bamboo agent
Asked by Vansh:

---


Answers:
author: Eduardo Alvarenga
body: Hello [@Vansh](/t5/user/viewprofilepage/user-id/4983288),**Welcome to Atlassian Community!**

#### CVS-2020-9488 {#toc-hId-150065223}

Atlassian classified it as a "low" based on its CVSSv3 base score (read more about [security levels for security issues](https://www.atlassian.com/trust/security/security-severity-levels)). Vulnerabilities in the low range typically have very little impact on an organization's business. The exploitation of such vulnerabilities usually requires local or physical system access. Vulnerabilities in third-party code that are unreachable from Atlassian code may be downgraded to low severity.

#### CVE-2022-23302, CVE-2022-23305, and CVE-2022-23307 {#toc-hId--1657389240}

Short answer: **Fix available**

Bamboo [8.0.6](https://confluence.atlassian.com/bamboo/bamboo-8-0-release-notes-1077903836.html), [8.1.5](https://confluence.atlassian.com/bamboo/bamboo-8-1-release-notes-1103070461.html) and [8.2.1](https://confluence.atlassian.com/bamboo/bamboo-8-2-release-notes-1115684503.html) contain a fix for those three CVEs. Please [plan to upgrade](https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html) at your earliest convenience.

As the [CVE-2022-22965](https://tanzu.vmware.com/security/cve-2022-22965) vulnerability (Spring4shell) was fixed on Bamboo releases [8.0.7](https://confluence.atlassian.com/bamboo/bamboo-8-0-release-notes-1077903836.html), [8.1.6](https://confluence.atlassian.com/bamboo/bamboo-8-1-release-notes-1103070461.html) and [8.2.2](https://confluence.atlassian.com/bamboo/bamboo-8-2-release-notes-1115684503.html) please consider those or later releases instead. Please keep an eye on our [FAQ for CVE-2022-22965](https://confluence.atlassian.com/kb/faq-for-cve-2022-22963-cve-2022-22965-1115149136.html) for more information.

Regards,

Eduardo Alvarenga  
Atlassian Support APAC
Bamboo spec files are not seen in Develop
Asked by Janus van Limpt:

We are currently experiencing an issue on Bamboo spec files and we hope you can help.

**The issue:**

We have created a simple spec file, this spec file runs fine while it's running from any branch. However, when we merge the specfile to develop (our default branch) it's not being detected by bamboo anymore. When we scan for specfiles (under linked repositories) it tells the scan went okay but gives the following message:

"07-Jul-2022 04:39:34 Bamboo Specs haven't been found in repository 'repo name'. All plans managed by Bamboo Specs stored in this repository will be disabled. If you haven't deleted Bamboo Specs intentionally, make sure you have placed your Bamboo Specs in the bamboo-specs directory under the repository root."

However, the file is there in bitbucket and when we check out our develop branch

If I change the linked repository branch back to my other branch the bamboo spec is imported. We have tried several things to resolve the issue but noting seems to work.

Some of the things we tried and observed are the following:

* If we fork the repository and try the same branch from the Fork it works fine without any changes
* If I create branch from develop and change the linked repository to that branch it works fine
* We tried clearing the cache on the bamboo server (\<bamboo_home\>/local-working-dir/serverSide/REPOSITORY_STORED_SPECS)
* We tried different file names (bamboo-specs/bamboo.yaml and bamboo-specs/bamboo.yml)
* We tried committing a simple (just echo) bamboo.yml file straight to Develop
* We tried creating another linked repository
* We disabled the bitbucket mirror

However, noting of the above seems to make any difference. We are highly depending on our develop branch so it is needed for us to get this to work.

Is there anything we can try to resolve this issue?

Regards,

Janus


Answers:
author: Mahesh Shinde
body: MAKE SURE THAT BITBUCKET SERVER AND BAMBOO ARE CONNECTED USING APPLICATION LINK  
Go to \> Manage apps \> Application links.  
MAKE SURE THAT BAMBOO SPECS PROCESSING IS ENABLED IN BAMBOO   
Go to \> Security \> Security settings. In the Repository Stored Specs security settings section select Enable Repository Stored Specs.  
MAKE SURE THAT BAMBOO SPECS IS ENABLED FOR A REPOSITORY YOU PUSHED TO  
Go to \> Build resources \> Linked repositories \> \<your repository\>.  
In the Bamboo Specs tab, enable Scan for Bamboo Specs.  
MAKE SURE THAT BAMBOO SPECS HAS ACCESS TO PROJECTS OR DEPLOYMENT PROJECTS YOU WANT TO MODIFY  
Go to \> Build resources \> Linked repositories.  
Select your Bitbucket Server repository.  
Select Enable all projects access or make sure that your build or deployments projects are listed in that section.


Tags: spec
Bamboo support for PostgreSQL 9.6?
Asked by Helen:

I'm planning an upgrade of all my Atlassian software, and obviously need to upgrade PostgreSQL at the same time.

Currently Bamboo 6.8.1 is connected to a PostgreSQL 9.6 database which also houses the rest of databases for the Atlassian tools.

When checking the supported versions, I can see that Bamboo 8.0 supports PostgreSQL 9.6, however versions 8.1 and 8.2 do not list it as supported. There is no notice that this version is deprecated.

Does anyone know definitively if Bamboo 8.2 supports PostgreSQL 9.6?


Answers:
author: Eduardo Alvarenga
body: Hello [@Helen](/t5/user/viewprofilepage/user-id/784933),

Bamboo 8.2 only supports PostgreSQL releases version 10.0 and later. For a complete list of compatible database versions please check the following page:

* [Bamboo Supported platforms - Databases](https://confluence.atlassian.com/bamboo/supported-platforms-289276764.html#Supportedplatforms-Databases)

Kind regards,

Eduardo Alvarenga  
Atlassian Support APAC

comments: author: Helen
body: Thanks Eduardo, that does answer my question.

As a follow up, could you please tell me why PostgreSQL 9.6 went from supported in Bamboo 8.0 to unsupported in 8.1 and 8.2 without being deprecated first?


author: Eduardo Alvarenga
body: Hi [@Helen](/t5/user/viewprofilepage/user-id/784933)

PostgreSQL 9.6 was "EOLed" by the PostgreSQL Global Development Group on 11/11/2021. For that reason, Bamboo had ended its support on that date.

* <https://www.postgresql.org/support/versioning/>

There is no strict policy on how long before a planned EOL a dependency component should be set as deprecated. Meaning that, for some products such as a database, we tend to support it for as long as possible, up to the last day.

If you are considering upgrading your PostgreSQL version, we advise you to move to version 11 or later as version 10 will have its final release on 10/11/2022.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC


author: Helen
body: Thanks Eduardo.

I was planning to move to PostgreSQL 11. It was just a matter of how many steps I needed. In this case Bamboo will have to go to 8.0 then upgrade PostgreSQL to 11, then upgrade Bamboo to 8.2.


Tags: postgres

server
Bamboo is not working!
Asked by Harry:

When I am starting bamboo as follows, I got the error message.

\> cd /opt/atlassian/bamboo/current/bin

\> ./start-bamboo.sh

Warning: To run bamboo in the foreground, start the server with start-bamboo.sh -f

I have started bamboo with tart-bamboo.sh -f command now bamboo is showing below error.

Error: Bamboo bootstrap failed: Failed to run pre-bootstrap upgrade tasks. Please contact Atlassian Support at [https://support.atlassian.com](https://support.atlassian.com/).

To resolve this, I have to add a new license in the bamboo.cfg.xml file. I have a server with centos, but I could not find bamboo.cfg.xml

Any solution!


Answers:
author: Nic Brough -Adaptavist-
body: What does the application log file say the problem is?

You don't put licences into config files, so doing that might actually be the problem - a corrupt config file could stop the startup.

comments: author: Harry
body: I have checked this doc for the same error.


author: Harry
body: <https://confluence.atlassian.com/bamkb/unable-to-run-pre-bootstrap-upgrade-tasks-as-your-support-period-has-ended-762874747.html>


author: Nic Brough -Adaptavist-
body: Ah, yes, sorry, I was confusing Bamboo with something in another question.

But the principles still apply:

* Is your config file correctly formatted (with the new licence)?
* What does the application log say the problem is?


author: Harry
body: Hello, I have solved the error.

Thanks,


author: Harry
body: I am facing another issue.

I have configured the SCP task in bamboo to copy the files to a remote server.

When I push any files from my local system, it reaches the bamboo server successfully, and builds are also created successfully.

But on the remote server, changes do not reflect. Any idea?


Tags: server
Is the REST API endpoint /plan/{projectKey}-{buildKey}/variables [POST] buged?
Asked by Jonathan Ghellere:

Hello Community,

I'm trying to create a variable in a plan using the REST API and cURL.

The following command works fine:

curl -k -H 'Authorization: Bearer XXXX' <https://localhost:8443/rest/api/latest/plan/AAAA-BBB/variables.json>

\[{"name":"aaa","value":"bbb"}\]

But when I try to send a POST request to add a new variable, I get the following message:

curl -k -H 'Authorization: Bearer XXXX' -H 'Content-Type: application/json' <https://localhost:8443/rest/api/latest/plan/AAAA-BBB/variables> -d '{"name":"ccc","value":"ddd"}'

"You must enter a valid variable name"

Is this a BUG?


Answers:
author: sunil jaiswal
body: I think it was a kind of bug they fixed it.

You can see this <https://jira.atlassian.com/browse/BAM-21787>
I can't connect to GitHub from Bamboo plugin using PAT
Asked by Nate:

We are using Bamboo version 6.10.2, when I attempt to connect to GitHub with username and PAT (in password field), I am able to load all my repos from Github, but when I go to test the connection, it fails saying:   

We couldn't connect to the repository. Here's what we got back:  
usage: git credential-store \[\<options\>\] \<action\>  
--file \<path\> fetch and store credentials in \<path\>  
usage: git credential-store \[\<options\>\] \<action\>  
--file \<path\> fetch and store credentials in \<path\>

remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead...


Answers:
author: Alexey Chystoprudov
body: Hi, it was fixed at Bamboo 7.1.3+, 7.2.0+

<https://jira.atlassian.com/browse/BAM-20748>


Tags: github
Run Plan at Git branch creation
Asked by Jozef Vandenmooter:

Does anyone know how to get Bamboo to kick off a Plan when a new branch is created in GitHub? It successfully creates a plan branch, but nothing else happens. I added a trigger to poll the repo, and then the plan runs when a change is made to the branch, but that's not what we want.

Thanks,

Jozef


Answers:
author: Jozef Vandenmooter
body: Tested this again and this actually works flawlessly in our server version of Bamboo (7.2.1 build 70207). I have no idea why I was first having issues getting this to work.

Jozef