youngmon/atlassian-qna huggingface dataset:
Suppression of alerts after hours
Asked by Rob:

Can you create a alert suppression for after hours? For example... alerts less than Critical from 1800 to 0900 weekdays would be suppressed until normal workday M-F 9-1800. Please advise and thank you in advance.


Answers:
author: Jack Brickey
body: Hi Rob, not w/in standard Jira notifications. Two things to consider here:

1. maybe you could disable notification and use Automation to replace notifications. Unsure how successful that would be TBH...just a thought.
2. consider an addon app, for example [smart-notifications](https://marketplace.atlassian.com/apps/1218580/smart-notifications?hosting=cloud&tab=overview) . I have no experience w/ this specific addon and there are others out there to consider.

comments: author: Rob
body: Hi Jack...this is not option with Opsgenie?


author: Jack Brickey
body: oops...very sorry Rob. I did not notice this was OG. my brain didn't switch out of Jira mode. Yes I'm sure you can suppress notifications based upon TOD in OG. Here is an article and video that might assist - [notification-rules](https://docs.opsgenie.com/docs/notification-preferences#notification-rules)


author: Rob
body: whoa...almost gave me a coronary ;0) ok I will give the video a peak


author: Nick H
body: Hi [@Rob](/t5/user/viewprofilepage/user-id/2013294) ,

You can suppress alert notifications during after hours / weekends using Notification Policies: <https://docs.opsgenie.com/docs/team-policies#notification-policy>

These can apply to specific alerts (anything less than P1), and during certain time intervals (after hours / weekends).

Your policy might look something like this:

![not pol comm 1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/120670iA200E414AC1F196D/image-size/large?v=v2&px=999 "not pol comm 1.jpg")


author: Rob
body: Perfect Nick..thank you


Tags: cloud
Adding tag to alert through action
Asked by Robin Sundstr?m:

Is there a way to add a predefined tag to arbitrary alert with an action ?


Answers:
author: Nick H
body: Hi [@Robin Sundstr?m](/t5/user/viewprofilepage/user-id/4075181) ,

You should be able to do this with an Alert Policy: <https://docs.opsgenie.com/docs/global-policies#alert-policy>

Alert Policies apply to alerts at creation and modify properties like the message, priority, or in your use case - add a tag. These can be configured globally and apply to all alerts, or under a team and apply to alerts only sent to that team.

Regardless - Alert Policies follow a simple IF / THEN conditional statement. "IF the alert has XYZ action, THEN add XYZ tag." Here's an example of what that might look like:

![action comm 1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/120399i480A95C171686729/image-size/large?v=v2&px=999 "action comm 1.jpg")

And here's a test of the policy applying to an alert at creation:

![action comm 2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/120400i910FBD0035E4970B/image-size/large?v=v2&px=999 "action comm 2.jpg")

Hope this helps with your use-case. Let us know if you have additional questions, issues, concerns, etc.

comments: author: Robin Sundstr?m
body: Thanks for the answer! I thought of that way too but wouldn?t it change the tag as the alert comes in if the action is added ? What I mean is then the execution of the action won?t add the tag. The thing is that the users should be able to add the tag by pressing the action. Cause when the tag is added a jira issue is created and the alert is closed.

Best regards


author: David Bell
body: [@Robin Sundstr?m](/t5/user/viewprofilepage/user-id/4075181) where you able to achieve this?


author: nicolasfortier75
body: any update on this? not working!


Tags: alert

cloud
What exit code is Bamboo expecting from a command to highlight text red in the log?
Asked by Hariprasad123:

I have a series of final tasks running in a job because I want them all to execute regardless of pass/fail result. One thing I would like to be able to do is easily differentiate failed results from a command task. What return status from the application is Bamboo expecting to flag the result this way in the log? I've seen it previously for failed results, but have yet to decipher the return status I need to provide to consistently do so.


Answers:
author: Richard White _TechTime_
body: Hi,

As I understand it, bamboo logs all stderr messages in red and stdout logs normally. I don't think it's related to the return code.
What can be used as Pattern when defining Artifacts?
Asked by Markus Petke:

I want to use simple Regex as Pattern, but it does not work.

I want to achieve somethink like "pre(con\|dition)\*"

So anything starting with precon and predition should match, but not for example pretest.

Is this even possible in Bamboo or can I just use the 3 mentioned here? <https://confluence.atlassian.com/bamboo/pattern-matching-reference-301663849.html>

Thanks in advance


Answers:
author: Richard White _TechTime_
body: Hi Markus,

Unfortunately, Bamboo uses [ant path matching,](http://ant.apache.org/manual/dirtasks.html#patterns) not regex. I don't believe there is a way to satisfy that in a single artifact pattern.

The only workaround I can think of, would be to define two artifacts (one for precon and one for predition in your example). Obviously that would not work for every use case though.

comments: author: Markus Petke
body: Hi Richard, thanks for the reply, even if it is not satisfying...

How do I use the ant-patterns? Do I simply put the html-style syntax as pattern?

From the examples on the site you posted, I could achieve my goal with some file-exclusions.


author: Richard White _TechTime_
body: Unfortunately, I think you can only use the actual path matching part.

In you example, the best you could do would be:

```
pre* 
```

which would obviously match both precon and predition as well as pretest.

I don't think there is a way to include the exclusions like in the ant reference. The original link you provided from Atlassian is pretty much all of the syntax that you can use.


author: robbytx
body: Hi Markus,

I was able to successfully use [Bash-style brace expansion](https://www.gnu.org/software/bash/manual/html_node/Brace-Expansion.html) for this in my Maven-based project:

```
test/target/{*.log,test-logs/**,failsafe-reports/**}
```

I think the equivalent for your question would be:

```
pre{con,dition}*
```

I hope that helps!

comments: author: inger_klekacz
body: This also works when defining the same Bitbucket Pipeline config for multiple branch name patterns. Thank you!
Bulk delete deployment projects
Asked by Maik:

Hello everyone, I just tried the remove plans bulk action in Bamboo administration, it worked fine but I could'nt find the remove deploy deployment projects action. Is it possible? I just erased 200 build plans and I want to delete the deployment projects too :(

EDIT: Currently using Bamboo 6.9.2

Thanks in advance


Answers:
author: Jeyanthan I
body: Hi [@Maik](/t5/user/viewprofilepage/user-id/1812884) ,

I'm afraid there is no option to do a bulk delete of deployment projects yet. You will have to manually delete them one by one. We have an open feature request. Please upvote and watch for updates.

* [BAM-18802 - Bulk delete option for deleting Deployment Projects](https://jira.atlassian.com/browse/BAM-18802)

Cheers,  
Jey
Need help setting up a secondary "slave" bamboo build server
Asked by Myke:

Hello,

Currently my company has a bamboo build server setup on a 2013 Mac Pro to build Unity mobile game titles for iOS and Android. What I'd like to do is make a secondary "slave" build server on a Windows based PC so that the main mac build server focuses on iOS builds and the slave one can focus on android builds. How would I go about doing this? I'm sure there is documentation on the site somewhere, but I just am not sure what I should be looking for. Any help would be greatly appreciated.

Thanks!


Answers:
author: Charlie Misonne
body: With a "slave" I suppose you mean a build agent and not a full Bamboo application server?

Normally you have only 1 Bamboo application with several agents. The agents can be local or remote. Local agents run on the same server as Bamboo while remote agents run on another machine.

You can install as many "remote agents" as your Bamboo license allows you to. The operating system of the bamboo agent does not matter.  
Here is the documentation about installing remote agents: [Bamboo remote agent installation guide](https://confluence.atlassian.com/bamboo/bamboo-remote-agent-installation-guide-289276832.html)

In order to define which builds will run on your Mac and which ones on your Windows agent you can use [build capabilities](https://confluence.atlassian.com/bamboo/configuring-capabilities-289277148.html).

comments: author: Myke
body: Yes! Remote agents, that's what I was trying to say. This is the info I'm looking for. Thank you so much :)


author: Charlie Misonne
body: you're welcome and good luck!


author: Myke
body: figured it out :p


Tags: android

ios

mac

windows
Can we execute jobs simultaneously in Bamboo without waiting for the first one to complete?
Asked by roshni sherkar:

Hi all, I am trying to execute 3 jobs linked in one plan in parallel but fail to do so as bamboo runs jobs in a sequential manner.

Is there any solution to get it implemented?

Any lead will be highly appreciated. Many thanks in advance.

Roshni.


Answers:
author: roshni sherkar
body: Hi,

I tried both the solution but the plans and jobs are getting executed in a sequential manner as I am having a single Agent.

Can we implement a parallel run with a single Agent?

comments: author: BRAJESH KUMAR SHARMA
body: Roshni,

A single agent can run only one job at a time. So your other job will be in queue until the one job get completed. You'll have to increase number of agents to run your jobs in parallel.

Other option you have, you can dockerize your single agent and create multiple nodes on an agent. So it can run multiple jobs in parallel on a single agent.


author: roshni sherkar
body: Hi Brajesh and Choon,

Thanks for getting back. I will try out both the solutions.


author: Choon Keat Seet
body: Alternative is to create the jobs in 3 different plans and have the same trigger.


author: BRAJESH KUMAR SHARMA
body: Roshni,

You can run the multiple jobs in parallel from the same stage only. If you have created the jobs in different stages then it will trigger one by one only.
Help me please find release date for 7.0.5 version
Asked by Galina Romanova:

Good day all!

We are waiting for 7.0.5 version, but I can't find information about it's release date. Will appreciate guidance

Thank you!


Answers:
author: Rohit B
body: I think it's 12 Dec 2019.

Please follow the below link:-

<https://confluence.atlassian.com/doc/issues-resolved-in-7-0-5-982324325.html>

comments: author: Jimmy Seddon
body: Hi [@Rohit B](/t5/user/viewprofilepage/user-id/4009923)

CConfluence 7.0.5 was released December 12, 2019. But I Beleive this question is asking when 7.0.5 will be available for Bamboo Server.


author: Galina Romanova
body: Yep Jimmy, you are right!


author: Jimmy Seddon
body: Hi [@Galina Romanova](/t5/user/viewprofilepage/user-id/3585697),

It doesn't look like Atlassian has made that information public yet. However, there is some speculation that can be made based on what information is available.

In the release notes: <https://confluence.atlassian.com/bamboo/bamboo-7-0-release-notes-989760226.html>  

You can see how long it has been in between each patch release, which would indicate that if another one is in the works it should be due soon.

You can also see that in Atlassian public Jira instance, if you search the Bamboo project for the "7.0.5" fix version: <https://jira.atlassian.com/issues/?jql=project%20%3D%20BAM%20AND%20fixVersion%20%3D%207.0.5>

All the issues targeting that release are currently in the status "Waiting For Release". While this doesn't give you an exact date and we won't have one until Atlassian announces it, it looks like it should be coming out pretty soon.

I hope that helps!

-Jimmy

comments: author: Galina Romanova
body: Hi [@Jimmy Seddon](/t5/user/viewprofilepage/user-id/512822) I just need to decide whether to go with 7.0.4 or in 2-3 weeks 7.0.5 will be available. Do you think 2-3 weeks is seems to be true?

Thank you!


author: Jimmy Seddon
body: [@Galina Romanova](/t5/user/viewprofilepage/user-id/3585697) looking at the issues that are targeting 7.0.5 is there anything there that you are waiting for because it affects your environment. If you are, it might be worth waiting for the 7.0.5 release, if there isn't anything you need from that list of issues and you were just waiting to be on the latest release I'd just move to 7.0.4. These are patch releases, there is likely to be a new minor release in the future you will want to upgrade to as well.

that's just my two cents.

I hope that helps!

-Jimmy


author: Galina Romanova
body: There are, but in 7.0.4 also, that is why i'm concerned )

thank you for advise!


author: Jimmy Seddon
body: This is quite the dilemma, unfortunately I don't think there is a enough public information to be able to say how soon 7.0.5 is going to be out. My best guess is really soon, But that is simply a guess I could be completely wrong.

Sorry I can't offer much more help on this one.

-Jimmy


Tags: release
Error while initializing Bamboo
Asked by test test:

Hi Team,

Help us to resolve below error.

You cannot access Bamboo at present. Look at the table below to identify the reasons:

TimeLevelTypeDescriptionException

|---------------------|-------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
| 2020-07-09 18:22:34 | fatal | bootstrap | Error while trying to initialise Bamboo Container. java.nio.file.AccessDeniedException: D:\\bamboo-home\\xml-data\\configuration\\cipher\\cipher.key_0 | N/A |

Please contact us at <https://support.atlassian.com/> if you have any queries.


Answers:
author: Alexey Chystoprudov
body: User which used to run Bamboo Server doesn't have access to D:\\bamboo-home\\xml-data\\configuration\\cipher folder. It's known issue <https://jira.atlassian.com/browse/BAM-18650> .

Please follow workaround section

comments: author: ?????? ????????
body: I have the same problem. Will you fix them?
Bamboo REST API versioning
Asked by fstr:

Hi, I'm using Bamboo 7.0.4.

I am successfully using the REST API to trigger Bamboo plans and requesting build result information.

```
https://bamboo.my.tld/bamboo/rest/api/latest/info
```

The Bamboo developer guide states, that the Bamboo REST API is using a [versioning scheme](https://developer.atlassian.com/server/bamboo/using-the-bamboo-rest-apis/#api-versions). The version *latest* will always point to the current version, but the API version can also be provided as an integer.
> The API version number is an integer, such as `1` or `2`.  
> The API version is independent of the Bamboo release number.

I quickly went through 1-10, and v1-v10, but none of them worked.

```
https://bamboo.my.tld/bamboo/rest/api/7/info
```

The feature to provide a specific version is very important, since the Bamboo instance and the applications that use the REST API are often maintained by separate teams. Additionally, a breaking change would bring down all API integrations if they point to *latest* and there would be no way to transition without downtime.

**Some questions around this:**

* Does the "versioning scheme" in the [developer guide](https://developer.atlassian.com/server/bamboo/using-the-bamboo-rest-apis/#api-versions) match the actual implementation?
* What is the current (Bamboo 7.0.4) API version for the REST API?
* Will a release of Bamboo always ship with (some or any) previous versions of the API?


Answers:
author: Gonchik Tsymzhitov
body: hi [@fstr](/t5/user/viewprofilepage/user-id/3988775) ,

Regarding the changes, I do support via wrapper from 5 to 7.

Mostly in practice not big changes in methods,

I do follow via next url for the double check

<https://docs.atlassian.com/atlassian-bamboo/REST/7.2.2/>

Cheers,

Gonchik Tsymzhitov


Tags: rest

rest-api

upgrade

version
JIRA and Bamboo + Bamboo Specs.
Asked by Sarathi Chatterjee:

We are trying to template our CD/CI pipeline including Deployments using Bamboo Specs.

We use Jira Service Desk for Change Management.

What we currently do is have a script task within the deploy-plan in which we pass the JIRA issue ID of the CHG to see if it approved and only then allow the deployment else fail it.

This works OK.

But if we have the deploy section also as a part of specs then we cannot inject variable to pass the JIRA issue ID.

we looked into using properties file to inject variables at build stage and this works fine - but then at deploy stage how do we inject a variable - as it is locked by specs ?

Thanks

Sar


Answers:
author: Richard White _TechTime_
body: Hi Sar,

As I understand it, you would like the same issue key variable to be used in build and subsequent deploy stage?

I think in this case you can use an inject bamboo variables task in the build stage, with scope set to "Result".

This should mean the variable is available in subsequent deploy stages, and you can use it in any deployment tasks.

comments: author: Sarathi Chatterjee
body: Hi Richard,

We went down this route. But the problem we have is that we may not know the issue key at build time and likely to know this very close to deploy time.

Trying to inject a variable at a later date will mean running a new build simply to inject a variable to be used in Deploy.

We want to be able to inject variable at deploy time.

Thanks


author: Richard White _TechTime_
body: Ah I see, so the problem is that you need to set the variables' value in between the time when the build was run and when the deployment was run.

In Jira Software, I know this can be done when you create a "release build" where you can override the deployment variables. I don't think that can easily work with JSD though, that is documented [here for JSW Cloud](https://support.atlassian.com/jira-software-cloud/docs/run-a-bamboo-build-when-releasing-a-version/)

Otherwise, I'm not sure how this can be easily done, after a bit of googling, I see this plugin is available: [Custom Deployments for Bamboo](https://marketplace.atlassian.com/apps/1216138/custom-deployments-for-bamboo?hosting=server&tab=overview) which seems like it might solve the issue? Note: I have never tried that particular plugin, so cannot attest to it being good or bad.

There is also a feature request to add this to the rest API, which would also solve your problem, consider voting for that if it would be useful: [BAM-18838](https://jira.atlassian.com/browse/BAM-18838)
currentUser() in Group Picker field JQL
Asked by Mathew Lederman:

Looking to find a way to find all issues where the currentUser() belongs to a Jira group selected in a group-picker field.

For example: Issues where Assignment Group (group picker field) is set to Zoom-Admins and I belong to the group Zoom-Admins.

In DC we're doing this with the Go! JQL plug-in, but it seems the same functionality doesn't exist in the Cloud due to some API restrictions where we have to use the Extended Search. However, this is tied to our IT Service Desk using a JSM project and to utilize the Queues we are limited to JQL functionality.

Any suggestions are appreciated.


Answers:
author: Mark Higgins
body: Hi Matthew,

Does this help?

Current User Context and User Membership Queries: Personalized Issue Searches using Jira JQL {#toc-hId--350691372}
------------------------------------------------------------------------------------------------------------------

The "Current User" context can be used with specific fields/custom fields like Reporter, Assignee, Watcher, Voter, and Any User Picker custom field.

Example: assignee = currentUser()

To get the list of issues where a user is part of a specific group in Jira, use the function "membersOf(GroupName)."

Example: assignee in membersOf("jira-administrators")

Regards Mark


Tags: assignment-groups

cloud

jira-service-management

jira-service-management-cloud
How to create an issue using API with a different reporter
Asked by Douglas Alves:

Hello guys, how are you?

I am trying to create an issue using an API but I don't why the reporter is always the same (me) maybe because I am using my API key.

I already tried to change the reporter in the payload putting a different reporter ID, it creates an issue but it keeps creating with me as reporter.

This s my payload

{  
"fields": {  
"project": {  
"id": "10001"  
},  
"summary": "Teste API 1",  
"issuetype": {  
"id": "10008",  
"reporter": {  
"id": "712020:2319a235-5b12-4bb9-94b9-55e698bf8df9"  
}  
}  
}  
}  
Do you guys know how can I do it?


Answers:
author: Mikael Sandberg
body: Hi [@Douglas Alves](/t5/user/viewprofilepage/user-id/5539978),

Welcome to Atlassian Community!

If you use the JSM endpoint for [Create customer request](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-post) you can select who the reporter should be by using raiseOnBehalfOf.


Tags: cloud

jira-service-management

jira-service-management-cloud
Best Practice for Managing External Service Desk when Office is Closed?
Asked by AS:

Hello, I am looking for advice for the management of External Service Desks.

- How do you manage federal holidays and service desk responses?

- How/Where do you manage auto-responses when the office is closed?

- Would this is automated? Or a manual process?

[@Ashton Bloom](/t5/user/viewprofilepage/user-id/5518178)


Answers:
author: Seon Shakespeare
body: Hi AS,

Managing service desks during closures takes a mix of clear communication and smart automation. Here's how I'd handle it:

**Before:**

* **Announcements:** Use the service desk announcement banner to display closure dates. You'll find this in your service desk project settings.

**During:**

* **Automated Responses (Jira Automation):**

  * **Auto-Acknowledge:** Set up a rule to automatically acknowledge new requests received during the closure.
  * **Set Expectations:** Include a message in the auto-acknowledgment stating that the office is closed and when they can expect a response.
  * **Categorisation/Prioritisation (Optional):** You can even use automation to categorise or prioritise requests that come in during the closure, making it easier to tackle them when you're back.

  *To set up these automations, go to "Project settings" -\> "Automation" within your service desk project.*

**Manual Processes (If Needed):**

* **Limited Coverage:** If you have a skeleton crew during the closure, adjust your auto-responses accordingly and set up a rotating schedule.
* **Emergency Contact:** For truly urgent issues, make sure your auto-response includes a clear escalation path or emergency contact method.

Basically, automate where possible, but keep a human touch for situations that need it.

Hope this helps!

comments: author: AS
body: Thanks [@Seon Shakespeare](/t5/user/viewprofilepage/user-id/2079193) We are currently managing 14 external service desks, so it is a bit cumbersome to update announcements, but not impossible. This number will only grown based on our trajectory. Was hoping to set an SLA and based on the calendar create an auto response on the holidays, but that is not in the function.

Suggestions for the automation below?

![Holiday Response.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/334790i5E05BEED74C8B960/image-size/large?v=v2&px=999 "Holiday Response.JPG")


Tags: cloud

jira-service-management

jira-service-management-cloud