youngmon/atlassian-qna huggingface dataset:
Incoming Call Routing - Keep trying forever?
Asked by Michael Easlick:

Hello!

Is there an option for Incoming Call Routing to keep trying forever, verse sending to voicemail or hanging up?  

For instance, if our escalation plan has 7 people, we want only those on-call to get the call which would be 2 people, so if I set it to two, after each person is called it will either go to voicemail or hang-up? What if I want it to keep calling over and over and never hang up?  

Just curious, we are not using this integration yet.


Answers:
author: Shashwat Khare
body: Hello [@Michael Easlick](/t5/user/viewprofilepage/user-id/5012707)   

No, we, unfortunately, do not have an option for the Incoming call routing to keep trying forever to reach an on-call engineer instead of routing to voicemail or hanging up.  

Yes, after the system performs the configured iterations of trying to connect to an on-call engineer via the incoming call routing, it will either go to the Voicemail if Voicemail is enabled for the Integration or will hang up the call.  

To achieve numerous attempts of calling the same on-call engineers until one of them acknowledges the alert, I would suggest you create repetitive Escalation Rules tagging both the Engineers in a loop, so as to escalate the call to the same on-call engineers again and again.  

PS: *An escalation can be configured to repeat at most **20** times for a single alert.* Best,  
Shashwat

comments: author: Michael Easlick
body: How does the configuration of the escalation affect the calls since it has the "acknowledge within X minutes" feature?

I would fill the new escalation with 20 entries of the primary and backup on-call users?


author: Shashwat Khare
body: Hi [@Michael Easlick](/t5/user/viewprofilepage/user-id/5012707) ,  

Yes, you would configure multiple rules of the same primary and backup on-call users to be tried unless somebody acknowledges the alert.  

Here's a document link that should help understand how these routing rules work in Opsgenie:  
[**A deep dive on Routing Rules**](https://community.atlassian.com/t5/Opsgenie-articles/A-deep-dive-on-Routing-Rules/ba-p/1330474)  

Best,  
Shashwat


Tags: cloud
How can people in our org create an alert/incident?
Asked by Alper Cugun:

I'd like to have some kind of facility for people to create either of these in Opsgenie.

I see there's the e-mail integration which will always work, but it's a bit bare.

The Slack integration only allows creating alerts but the slash command is very difficult to use.

Is there some kind of form or form builder that people can trigger (on a URL, in Slack) and have pre-populated fields to call something in with?


Answers:
author: Nick H
body: Hi [@Alper Cugun](/t5/user/viewprofilepage/user-id/4370663) ,

The Email integration would probably be the easiest. You could share the integration's address with the facility, and an alert can be created anytime an email is received.

Otherwise if you use other ticketing tools like Jira, JSM, Zendesk, etc. - those would be great alternatives.


Tags: cloud
Can a Slack Connect user use the Opsgenie/Slack integration?
Asked by Dave Beaudoin:

We have Opsgenie and have setup Slack integration with it. We want users from another org in the channel to be able to use this. Will users connected via Slack Connect be able to use the Opsgenie integration?


Answers:
author: Nick H
body: Hi [@Dave Beaudoin](/t5/user/viewprofilepage/user-id/4808680) ,

Outside users should still be able to preform **/genie** commands on an alert, or select the default buttons available within the Slack alert - as long as your do not enable the Require Matching a User option:

![slack1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/246178iE99964ABD248A84B/image-size/large?v=v2&px=999 "slack1.jpg")

User will have to connect their Slack accounts to Opsgenie using **/genie connect** command if that is enabled, and they will also need to be an Opsgenie user in order for that to authenticate.

comments: author: Dave Beaudoin
body: Thank you for the response! We'll test this and report back!


author: Dave Beaudoin
body: Looks like we run into an error that seems to suggest that the user will require OpsGenie integration setup in their Slack.

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


Tags: cloud
Opsgenie alerts being ignored
Asked by Carol Saldanha:

Hi all,

We have configured an Opsgenie/Jira integration which has been working seamlessly.

In the last couple of weeks we have noticed that a couple of alerts were 'ignored' by Opsgenie so the team were not alerted. Upon checking I found that an 'Ignore' action had been set in the Opsgenie Integration. I have now deleted this and the alerting is working again.

I'd like to check the logs to see when this may have been set but can't seem to go back beyond 2nd March. Is there any way to search logs before that date? Is there anywhere else I can look (apart from the Debug/logs menu) to find out what may have changed?

Carol


Answers:
author: Nick H
body: Hi [@Carol Saldanha](/t5/user/viewprofilepage/user-id/4649403) ,

Logs are only retained in the UI for 13 days.

Opsgenie does have a [Logs API](https://docs.opsgenie.com/docs/logs-api) which shouldn't have a limit on pulling past logs, but this in only included with the Enterprise plan at this time.


Tags: cloud
cURL Variable as Attachment to Alert API
Asked by Andrew Katz:

Hello,

Is there a way to use cURL to add a variable as an attachment to an alert using the Alert API in OpsGenie?

The documentation shows how to do this using a file on the filesystem, but I am hoping to include a BASE64-encoded variable of a string/some JSON and upload that as an attachment instead.

Is this possible through the OpsGenie Alert API? I have tried a number of ways of formatting it but still getting a 400 error saying:

```
Required request part 'file' is not present
```

Thank you!


Answers:
author: Justin Sitarz
body: Hi Andrew!

Justin here, from Opsgenie support - happy to help!

An alert attachment is required to be a file, so in your example, you would probably want to generate a file (perhaps just a .txt or .json file) locally, containing your string or JSON prior to making the actual request to Opsgenie to add that newly generated file as an attachment.

If you're wanting to simply add some plain text to an alert, your best option would instead be to add it as a note, using the Add Note method outlined here:

<https://docs.opsgenie.com/docs/alert-api#add-note-to-alert>

Let me know if that helps to answer your question, or if there's anything else I could assist with!

Best,

Justin Sitarz

Cloud Support Engineer, Opsgenie


Tags: cloud
OEC/OpsGenie public issue tracker
Asked by Tom DuVally:

This OEC GitHub issue [oec #52](https://github.com/opsgenie/oec/issues/52#issuecomment-1269875482) was resolved saying a public issues tracker in Jira was available, but I can't find it anywhere. Since the code hasn't been updated in years I was hoping to find out the current status of the project. They say it's not dead, but it sure seems that way.

Does anyone have a link or could tell me how to find it?


Answers:
author: John M
body: Hi Tom,

OEC is alive. You can see issues related to OEC and Opsgenie here:

[https://jira.atlassian.com/browse/OPSGENIE-1038?jql=text%20\~%20%22oec%22](https://jira.atlassian.com/browse/OPSGENIE-1038?jql=text%20~%20%22oec%22)
Could not send [createIssue] action to JiraServiceDesk, error 400
Asked by Andr?s Enrique C?rdenas:

I've been trying to create an integration between Opsgenie and Jira Service management, that whenever we receive an alert from our monitoring system in Opsgenie (which is currently working, Zabbix 6.0.13) a ticket is created with that information in Jira Service management.

I've followed the documentation (keeping in mind NOT to check OEC), using the right project Key, API token for an user with enough permissions, etc.

I'm getting the following:

\[system\] Could not send \[createIssue\] action to JiraServiceDesk \[Zabbix to JIRA\]. Reason: 400 Bad Request: "{"errorMessages":\[\],"errors":{"labels":"Field 'labels' cannot be set. It is not on the appropriate screen, or unknown."}}"

{  
"alertLogOwner": "System",  
"responseBody": "{\\"errorMessages\\":\[\],\\"errors\\":{\\"labels\\":\\"Field 'labels' cannot be set. It is not on the appropriate screen, or unknown.\\"}}",  
"_outgoingData": {  
"_headers": {  
"-Content-Type": \[  
"application/json;charset=UTF-8"  
\],  
"-Authorization": ........  
\]  
},  
"integrationType": "JiraServiceDesk",  
"_payload": {  
"_fields": {  
"summary": "\[Zabbix\] Alert from Zabbix",  
"-labels": \[  
"fromOG"  
\],  
"_project": {  
"key": "IT"  
},  
"_issuetype": {  
"name": "Incident"  
},  
"description": "The alert has no description."  
}  
},  
"integrationName": "Zabbix to JIRA"  
},  
"alertId": "7277dde3-48a4-4d86-bb50-0d514e12ef48-1678750074990",  
"alertLogType": "system",  
"statusCode": "BAD_REQUEST"  
}

Would appreciate any help you guys can provide.


Answers:
author: Nick H
body: Hi [@Andr?s Enrique C?rdenas](/t5/user/viewprofilepage/user-id/5166356) ,

You should be able to correct this in JSM by navigating to the Settings menu ? Issues tab ? Screens tab ? Configure the same project's screen that is configured in the integration's action mapping section:

![jsm4001.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/245550iF26FDB7353F2C7C9/image-size/large?v=v2&px=999 "jsm4001.jpg")

Add any fields to this Screen that appear in 400 error (labels, summary, description, etc.):

![jsm4002.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/245551i60623C9E48CBCC25/image-size/large?v=v2&px=999 "jsm4002.jpg")

If the Labels field exists under this screen, another way to check within JSM is by creating an issue under the project in question, and selecting the *Find your field* option:

![jsm4003.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/245552iFC74CE1ABEAB4EC3/image-size/large?v=v2&px=999 "jsm4003.jpg")

If you search for the Label field (or any in general), there should be an error if the field does not exist in the project / issue. You should also then be able to click into Screen where it needs to be added:

![jsm4004.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/245553iD5C7B6F84F13A918/image-size/large?v=v2&px=999 "jsm4004.jpg")

comments: author: Andr?s Enrique C?rdenas
body: thank you, that was pretty easy to follow and solve, tickets are now being created in JIRA.


Tags: jira-service-desk
Bamboo Database Table/Field Location of Projects/Linked Repo controlled via Bamboo Specs
Asked by Conor O'Higgins:

Hi,

I'm trying to find the location in the DB for the field(s) that stores the status of a project that is controlled via Bamboo Specs. Such as on the UI as shown below:  

![Screenshot 2022-08-10 at 16.23.08.png](https://community.atlassian.com/t5/image/serverpage/image-id/210483i1B334A64C9EDF022/image-size/large?v=v2&px=999 "Screenshot 2022-08-10 at 16.23.08.png")

There is a db table ***vcs_location*** that has a ***xml_definition_data*** that captures all of the repository settings however the config ***bamboo.specs.enabled*** captures which projects have specs enabled as an option in the UI but it doesn't differentiate between projects that are controlled by specs and those that aren't but only have the setting enabled.

The bamboo version I'm using is: 7.1.1  

Thanks.


Answers:
author: Eduardo Alvarenga
body: Hi [@Conor O_Higgins](/t5/user/viewprofilepage/user-id/4933493)

The information you are looking for is contained in the **PLAN_VCS_SPECS_SOURCE** table. Here is a query that will return the *Plan Id* , *Plan Key* and *RSS repository name*. You can adapt it to your specific requirement.

```
SELECT S.PLAN_ID  AS "Plan?Id",
       B.FULL_KEY AS "Plan?key",
       VL.NAME    AS "RSS?Repository"
FROM   PLAN_VCS_SPECS_SOURCE S
       JOIN BUILD B
         ON B.BUILD_ID = S.PLAN_ID
       JOIN VCS_SPECS_SOURCE V
         ON V.VCS_SPECS_SOURCE_ID = S.VCS_SPECS_SOURCE_ID
       JOIN VCS_SPECS_STATE VT
         ON VT.VCS_SPECS_STATE_ID = V.VCS_SPECS_STATE_ID
       JOIN VCS_LOCATION VL
         ON VL.VCS_LOCATION_ID = VT.VCS_LOCATION_ID 
```

Kind Regards,

Eduardo Alvarenga  
Atlassian Support APAC

comments: author: Conor O'Higgins
body: Thanks [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) this worked a treat. Thanks!


author: Eduardo Alvarenga
body: Thank you [@Conor O_Higgins](/t5/user/viewprofilepage/user-id/4933493)

I've created a KB article that demonstrates that and more:

* [How to locate Build plans an Deployment projects/environments that are bound to Repository Stored Specs](https://confluence.atlassian.com/bamkb/how-to-locate-build-plans-an-deployment-projects-environments-that-are-bound-to-repository-stored-specs-1157178569.html)

Regards,

Eduardo Alvarenga  
Atlassian Support APAC


Tags: database

spec
Can I extend the length of the bamboo variable?
Asked by Trushant Limbani:

Currently, bamboo only allows for a variable length of 4,000. Can we extend that?


Answers:
author: Santhosh Thokur Raghava
body: Hi [@Trushant Limbani](/t5/user/viewprofilepage/user-id/5007023) ,

Thank you for reaching out to Atlassian Community.

Which version of Bamboo are you using? This issue was fixed in 7.2.0 and 7.1.2 as per [BAM-21059](https://jira.atlassian.com/browse/BAM-21059?src=confmacro)

Please let us know if you see otherwise.

Thank You,  
Santhosh Thokur

Atlassian Support AMER

**--please don't forget to Accept the answer if the reply is helpful--**

comments: author: Trushant Limbani
body: Even after using Bamboo version 8.1.1, I continue to receive this error. I have attached a screenshot of the error.  

![bammboVersion.png](https://community.atlassian.com/t5/image/serverpage/image-id/216321i59ACB5DB82170D63/image-size/large?v=v2&px=999 "bammboVersion.png")![Error.png](https://community.atlassian.com/t5/image/serverpage/image-id/216320i78984222E979BA51/image-size/large?v=v2&px=999 "Error.png")  

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


author: Santhosh Thokur Raghava
body: Hi [@Trushant Limbani](/t5/user/viewprofilepage/user-id/5007023) ,

Thank you for providing additional information.

We would request you to raise a Ticket at [Atlassian Support.](https://support.atlassian.com/contact/#/)

Thank You,  
Santhosh Thokur

Atlassian Support

**--please don't forget to Accept the answer if the reply is helpful--**


Tags: variable
Bamboo Service issue
Asked by Teodora Janicijevic:

Hello,  

I installed Bamboo agent with command

**java -Dbamboo.home=\<BAMBOO_AGENT_HOME\> -jar atlassian-bamboo-agent-installer-7.2.4.jar** [**https://bamboo.xxx.com/agentServer/**](https://bamboo.resideo.com/agentServer/)

<br />

But, it's not online and when I try to start it I get this mistake:  

ERROR \| wrapperm \| 2022/08/10 09:49:13 \| The Bamboo Remote Agent service is not installed - The specified service does not exist as an installed service. (0x424)

When I did this command before Service was installed automatically, but now when I go to services there is no Bamboo service.   

Is it possible to install it now additionally?


Answers:
author: Vani
body: Hi [@Teodora Janicijevic](/t5/user/viewprofilepage/user-id/5005161) ,

Thank you for posting your question in Atlassian Community.

Please check this Bamboo Knowledge Base article on [How to Run, Install, Start, and Stop Remote Agents](https://confluence.atlassian.com/bamkb/how-to-run-install-start-and-stop-remote-agents-958455495.html).

You can issue this command now to install as a service.

\<`bamboo-agent-home>\bin\InstallBambooAgent-NT.bat`

Please let us know if you face any issues.

Thanks

Atlassian Support

comments: author: Teodora Janicijevic
body: Hello,

Thank you for quick response.

Running this script fixed my issue. Thanks!

Best regards,e

Teodora Jani?ijevi?


author: Vani
body: Hi Teodora,

Great to hear. Have a nice day.

Thanks

Atlassian Support
With bamboo-specs yaml is it possible to have a base deployment and merge yaml maps?
Asked by Jay Barra:

I have multiple environments I deploy a project to where the only difference in the deployment are the variables associated and the triggers.

How can I specify a base deployment job and use the merge keys feature in the yaml-specs reader together?

What I want to achieve would be this.

```
---
version: 2
deployment:
  name: Multi-env deployment
  source-plan: MY-PROJ
release-naming:
  version-name: release-1
environments:
  - ENV-A
  - ENV-B
  - ENV-C

BASE: &deploy
  tasks: 
    - clean
    - script
        interpreter: SHELL
        scripts:
          - echo ${bamboo_ENV_SPECIFIC}
  variables: &base-variables
    foo: bar
    fiz: baz

ENV-A:
  <<: *deploy
  variables:
    <<: *base-variables
    ENV_SPECIFIC: A

ENV-B:
  <<: *deploy
  variables:
    <<: *base-variables
    ENV_SPECIFIC: B

ENV-C:
  <<: *deploy
  variables:
    <<: *base-variables
    ENV_SPECIFIC: C
```

But I get validation errors saying that BASE is an unused variable. Is my only option to move BASE into ENV-A?


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

Bamboo will expect all declared variables to be used. That's part of the YAML optimisation.  

Considering "ENV-A" is your "template" environment. You can use the following to achieve the same results:

```
---
version: 2

deployment:
  name: Multi-env deployment
  source-plan: DEF-DEF

release-naming:
  next-version-name: release-1

environments:
  - ENV-A
  - ENV-B
  - ENV-C

ENV-A:
  tasks: &base-tasks
  - clean
  - script:
      interpreter: SHELL
      scripts:
      - echo ${bamboo_ENV_SPECIFIC}
      description: test
  variables: &base-variables
    ENV_SPECIFIC: A
    foo: bar
    fiz: baz

ENV-B:
  tasks: *base-tasks
  variables:
    <<: *base-variables
    ENV_SPECIFIC: B

ENV-C:
  tasks: *base-tasks
  variables:
    <<: *base-variables
    ENV_SPECIFIC: C
```

<br />

Kind Regards,  

Eduardo Alvarenga  
Atlassian SupporT APAC
Disable git Bamboo Proxy for Source Checkout
Asked by Patrick Schneider:

Hi,

is there a way to disable the Bamboo Proxy for Git when using the Source Code Checkout Task and just use the native git command.

Best

Patrick


Answers:
author: Eduardo Alvarenga
body: Hello [@Patrick Schneider](/t5/user/viewprofilepage/user-id/711920)

As mentioned by [@Charlie Misonne](/t5/user/viewprofilepage/user-id/502263) the purpose of the Checkout/Pull/Push tasks is to exactly overcome authentication issues by using a proxy that would do the heavy lifting.

If you have a particular reason to use a direct git interaction, you need to use a script task.

We have a nice KB that explains how to use that alternative method.

* [How to perform a Git SSH checkout from a Bamboo Script Task](https://confluence.atlassian.com/bamkb/how-to-perform-a-git-ssh-checkout-from-a-script-task-741999875.html)

Thank you,

Eduardo Alvarenga  
Atlassian Support APAC


author: Charlie Misonne
body: Hi Patrick,

If you want to use the direct GIT URL's you should use a script task instead of a source code checkout task. I don't think there is an option in the source code checkout task to bypass the proxy mechanis of Bamboo.

Something like this should work:

```
git clone <your-url>
```

Of course you need to take care of authentication parameters yourself by using encrypted variables or options like *--depth 1* for a shallow clone.

If you keep the connection between build and only omit the source code checkout task you can still use the URL of the repository like this:

```
git clone ${bamboo.planRepository.repositoryUrl}
```


Tags: server
Mutlitple word combinations trigger for a rule
Asked by Jurjen Geleijn:

Hi guys,

I need some help here as i can't figure out how to do this.

I want a rule to check the start of a comment and then if it contains either :(1)"Delegated to", or (2)"Reassigned to" or (3)"Relegated to" i want to move it to a specific list. I managed to do this with three different rules, one to check for word (1). a new rule to check for word (2) and a third to do number (3).

Can this also be made to fit in a single rule trigger? So:

"If a comment starting with: "Delegated to", or "Reassigned to" or "Relegated to" is posted to a card."...

By my knowledge you cant use any variant of an "OR" statement.

Would greatly appreciate your help!


Answers:
author: Eduardo Alvarenga
body: Hello [@Jurjen Geleijn](/t5/user/viewprofilepage/user-id/5001006) welcome to **Atlassian Community!**

As this question was posted to the Bamboo forum, I just wanted to understand if that's either a Jira or Bamboo question. Can you please clarify?

Bamboo also has special 'trigger' conditions that may be used, but not sure if they rely to "cards" as you are describing.

Eduardo Alvarenga  
Atlassian Support APAC

comments: author: Jurjen Geleijn
body: Hello [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410)

Thanks for your welcome, I now see that I am in the wrong section of this forum. It was meant for trello actually.

I don't know how this went wrong, but thanks for pointing that out, ill move the question.


author: Sue Wilson
body: Hi [@Jurjen Geleijn](/t5/user/viewprofilepage/user-id/5001006)

Have you tried the "If/Else Block" condition?

IF  
comment contains "Delegated to", move to specific list

ELSE IF  
comment contains "Reassigned to", move to specific list

ELSE IF  
comment contains "Relegated to", move to specific list

Same premise, but all in one automation rule.


Tags: trigger
Share java spec commit id with generated build plan
Asked by Erwin K_:

I have a configuration of a repository with a java build spec and multiple other repositories with source code. The build specs generate similar build plans for each repo.  

I want to have traceability between the build results of each repo and the version (e.g. the commit id) of the build spec used to create the build plan.  
How to realize this traceability?  

I was thinking of setting a plan property when the buildspec is run, but how to retrieve its commit id?  

Another starting point would be to somehow add a build step, querying the last successful build of the java spec.


Answers:
author: Eduardo Alvarenga
body: Hello [@Erwin K_](/t5/user/viewprofilepage/user-id/4998399), welcome to **Atlassian Community!**

You can use the **bamboo.planRepository.\<position\>.revision** variable to retrieve the *revision id* for that commit. The *\<position\>* starts on 0 and depends on how your Specs repository is ordered on the Plan.

To automate that, you can script something that would scan all environment variables named **bamboo.planRepository.\<position\>.\<name\>** , where *\<name\>* is your Specs repository, then strip the *\<position\>* from it and reuse it as the *\<position\>* on **bamboo.planRepository.\<position\>.\<revision\>**.

* [Bamboo variables](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html)

Optional: Once you have the revision you can create a text file with the *variable=value* format and reuse it across multiple Jobs if required:

* [Configuring a variables task](https://confluence.atlassian.com/bamboo/configuring-a-variables-task-687213475.html)

Kind regards,  

Eduardo Alvarenga  
Atlassian Support APAC

comments: author: Erwin K_
body: Thanks this has been useful!  
Previously I only had the code repo linked to the plan. By adding the specs repo to the plan as well, it can be accessed to retrieve the last commit.