youngmon/atlassian-qna huggingface dataset:
Will it possible to upgrade bamboo from version 6.3.1 to 6.10.3?
Asked by Mat:

This is the upgrade path I got it from your documentation when upgrading from very old versions of Bamboo.

* When upgrading from Bamboo 5.14 and later, follow this upgrade path:

**5.14+ ? 6.5 ? LATEST**

**[Ref: https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html#Bambooupgradeguide-Upgrade_export](https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html#Bambooupgradeguide-Upgrade_export)**

* Need to understand is there any possible way that I can upgrade the version as I mentioned in the title?
* The following add-ons are incompatible when I do the Bamboo update check for 6.10.3

  |------------------------------|----------------------------|---------------------|
  | Add-ons                      | Latest available Add-ons-V | Compatible Bamboo-V |
  | Atlassian REST API Browser   | 3.2.2                      | 6.7.3               |
  | Hung Build Killer for Bamboo | 3.0.15                     | 6.3.4               |
  | Plan Runners for Bamboo      | 3.6.5                      | 6.10.3              |
  | Chef cookbook tests          | 1.11                       | 6.8.3               |
  | Variable tasks for Bamboo    | 1.1.24                     | 6.9.2               |
  | Build Times for Bamboo       | 1.1.9                      | 6.7.3               |
  | Zephyr Enterprise for Bamboo | 1.4.1                      | 6.6.3               |


Answers:
author: Jimmy Seddon
body: Hey [@Mat](/t5/user/viewprofilepage/user-id/3647470),

Welcome to the Community!

\*\*\*Edit\*\*\* My bad, I went back and looked and we actually upgraded to 6.5.1 ahead of upgrading to 6.9.2.

Looking at the release notes \& the upgrade notes, I believe there are some larger changes from a DB migration perspective that require the intermediate upgrade. So in that case I would recommend upgrading to 6.5.x ahead of going to 6.10.3

\*\*Also\*\* if you look at the 6.4.x upgrade notes, you will see this note:  
"Bamboo 6.4 is shipped with a native mechanism for monitoring builds. For that reason, the Hung Build Killer plugins becomes deprecated."

As for app compatibility, you need to decide if those apps are mandatory to have running upon upgrading to the newer version of Bamboo, in which case you will want to make a request to the app creators in the marketplace to update their apps to be compatible with the latest version. If you can live without any or all of them then you can upgrade and disable the incompatible apps until they are updated to support the 6.10.3 version.

TL;DR;

You should start with an upgrade to Bamboo 6.5.x, all of your existing apps are supported on that version. From there read my comments about app compatibility.

I hope that helps!

-Jimmy
If my plan has multiple stages can you deploy if stage one is completes
Asked by David McFadden:

I have a build plan where i want to complete a security scan as part of stage 2, the scan is slow and i dont want it to be a blocker for deployments.

My question is after the "build" stage completes, can i mark it as complete so it is available to be deployed? I would like it to work similarly to the manual stage, where the build is available for deployment with no restrictions on the fact that all stages have not been run.


Answers:
author: Jimmy Seddon
body: Hi [@David McFadden](/t5/user/viewprofilepage/user-id/3647778),

Welcome to the Community!

Are you wanting to be able to deploy the build to a QA environment so that testing can begin while the security scan is running? If that is the case how long do your deployments take? It might be reasonable to make stage 2 the deployment to QA, and then stage 3 is the security scan?

Just a thought.

-Jimmy


Tags: automation

plan

script
Bamboo installation creates the following path on linux
Asked by mduduzi ndlanzi:

i\`m installing bamboo from stretch on a Centos 7 linux server and i notice the following path.

/opt/bamboo/bamboo/bin/C:

not sure if that path should be there


Answers:
author: Daniel Santos
body: Hello [@mduduzi ndlanzi](/t5/user/viewprofilepage/user-id/3135380)

This is strange, it shouldn't be there!

* Can you share the set of steps you use for this installation?
* Is this a clean installation (with no prior data) OR are you installing and migrating content from another server?
* Are you following the steps described in this document?
  * [Installing Bamboo on Linux - Atlassian Documentation](https://confluence.atlassian.com/bamboo/installing-bamboo-on-linux-289276792.html)

Understanding the steps you are following will probably help me identify what is causing the issue.
Audit logs are not getting generated
Asked by Qualys DevOps:

For any of the plans in bamboo, we are not seeing any audit logs. We tried to disable and re-enable it, but still not working. What is the reason that audit logs stopped coming up suddenly, and what the way out now, how do we enable it and get it working?


Answers:
author: Daniel Santos
body: Hello there!

I was able to find another case in our support system with similar behavior. There is a problem with the **AuditLogSaveThread**in handling some exceptions (e.g. DB persisting issues). The thread may die silently leaving the Bamboo server up and running without the audit support. This problem was reported in this bug:

* [\[BAM-18855\] Improve audit log handling code - Create and track feature requests for Atlassian products.](https://jira.atlassian.com/browse/BAM-18855)

Are you able to schedule a restart of your server to check if this will bring the audit log feature back running?

comments: author: Daniel Santos
body: Hi [@Qualys DevOps](/t5/user/viewprofilepage/user-id/899422)  

I hope you are doing great!  

Were you able to restart the server?  
Are things are working now?
bamboo.yaml new error on import: Task must have its type defined as the only YAML property
Asked by George Worthington - NOAA Affiliate:

```
Have been experiencing a new Bamboo import failure after recent changes. I have reverted to a known good version of the bamboo.yaml spec file, (reverted to the good commit via git) however the error remains.  Any ideas if a recent change to Bamboo spec file imports or something else could be at play?



```


Answers:
author: George Worthington - NOAA Affiliate
body: This turned out to be somewhat obvious - the bamboo-specs are only read from the Master branch, changes had been made to our development branch and the bamboo import didn't break until days later after a merge was conducted to Master. Long story short, only change your bamboo-spec on your master branch.
Password variable contains backticks, substitution fails in deployment plans
Asked by Michael:

Say my MySQL password looks like this

```
T#`DEAE&H29r23328h23c@#X21
```

which contains a backtick. Of course, it might contain a " or ' or $ or other expandable sequence.

When variable substitution occurs in a deployment plan

```
MYSQL_PASSWORD=********
```

I get this error

```
error 20-Nov-2019 13:47:21 bash: -c: line 11: unexpected EOF while looking for matching ``' error
20-Nov-2019 13:47:21 bash: -c: line 37: syntax error: unexpected end of file
```

How can I ensure that variables are *safely substituted* in deployment (and, presumably, build) plans and ensure they are *not interpreted*?

Of course, I could create only alphanumeric passphrases, but that reduces entropy somewhat and I don't want to limit our infrastructure configuration. Do I need to use Bamboo Specs or something?

We're running self-hosted Bamboo version 6.3.4 build 60309 - 24 May 18


Answers:
author: Daniel Santos
body: Hi [@Michael](/t5/user/viewprofilepage/user-id/822579)

Thank you for raising this question.  

Global, plan and deployment variables can be evaluated in tasks by using the following format:

```
${bamboo.<variableName>}
```

Please notice that this evaluation takes place before the task is executed.

Let's suppose you are adding the following line in your inline script:

```
VAR1=${bamboo.myVariable}
```

Before bash is called the variable is already substituted and you have the error mentioned.

```
...bash: -c: line 11: unexpected EOF while looking for matching...
```

<br />

**How to avoid this?**

Use a different variable formating.

We have two ways to mention a variable:

1.

   ```
   ${bamboo.<variableName>}
   ```

   Evaluated before the build
2.

   ```
   $bamboo_<variableName>
   ```

   Available only when the bash script is run

**How to move forward?**

Please use the second format in inline scripts. It will prevent anomalies caused by strange characters that may be part of your variables.

Another option is to make sure the content of your variables is surrounded by single quotes ( *'content' ).*

I hope that helps

comments: author: Michael
body: It does; thank you!

One clarification: how should I use [Bamboo variables that have dots in their names](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html), like \`bamboo.deploy.environment\` ?

```
$bamboo_deploy_environment 
```

or

```
$bamboo_deploy.environment 
```

?

Presumably I should convert all \`.\` to \`_\` ?


author: Daniel Santos
body: Yes, convert all of them to underscores "_".  
You should be able to see all the variables available in your build log file.  
Try to search for one that you know and you should find all of them together.  

=\]  


Tags: deployment

script

variable
Bamboo bootstrap failed
Asked by mduduzi ndlanzi:

Bamboo bootstrap failed: Your Bamboo instance could not start because health check failed. Contact Atlassian Support


Answers:
author: Edwin Kyalangalilwa
body: Hi [@mduduzi ndlanzi](/t5/user/viewprofilepage/user-id/3135380) ,

Please check for any errors during startup in the Bamboo log file.

```
<bamboo-home>/logs/atlassian-bamboo.log
```
Build fails with "No failed test found. A possible compilation error occured" on script task
Asked by Michael Moore:

Just trying to move to Bamboo from TeamCity. This is my first small task.

I use a Script Task to compile my GoogleTest C++ code which has some intentional code that causes warnings in the compile (think passing null pointers to test how it is handled).

All my tests pass, but the overall build fails due to the compilation warnings stated above.

My question is if there is anyway to have bamboo ignore these warnings? I do not want to turn off the warnings in my compile as this could cloak problems in non-test code.

If it makes a difference, my build agent is running on a RHEL7 virtual machine.


Answers:
author: Michael Moore
body: Never mind. The build was failing due to an artifact not being created with the proper name. Was at the end of the log and I was fixated on compile warnings.

comments: author: nithyananthaml@hcl.com
body: Hi Michael Moore,

We are getting this kind of error "No failed test found. A possible compilation error occurred." in Bamboo build logs...?

Why bamboo is not properly parse the build logs..?


author: Michael Moore
body: Hey,

It has been a long time, but we had misspelled an artifact (product RPM) and it wasn't finding the one it was looking for so tests didn't run.

I'm afraid I don't remember anything more specific.

Mike
Jira Service Desk automation to find duplicate Service requests based on the summary field
Asked by Jonathan Lewis:

Hi Atlassian Community,

Apologies I'm still somewhat a beginner on the automation side of things for Jira!

I'm looking to add an automation rule to our Jira Service Desk in order for it to pick up any duplicate tickets based on the summary field contents and then to transition the ticket into a resolved/cancelled status.

Example from my screenshot:

I have 3 tickets created which are under the same "request type" and contain the same summary (in this case summary = "123456789") with the status "waiting for support". I want the initial ticket (PSP-70) to be the original and any others the come through after with the same summary field (not pre-defined if possible) to be moved to resolved/cancelled status.

![JSD test 1.png](/t5/image/serverpage/image-id/329316i33D9A1C05C6B1372/image-size/large?v=v2&px=999 "JSD test 1.png")

*** ** * ** ***

Below is what I have currently for the Automation rule.

It looks up the issues fine, but I think where I'm stuck at is the compare part of the rule...

![JSD test 3.png](/t5/image/serverpage/image-id/329318iB5EE33855751929D/image-size/large?v=v2&px=999 "JSD test 3.png")

*** ** * ** ***

I'm wanting the flow to be like below:

-Lookup issue- If Jira Ticket:

* = active
* = service request
* = waiting for support
* resolution date is empty

-Compare- Then check other tickets that are with the above same criteria:

* Active
* Not set to resolved/no resolution yet
* AND whether the "summary field" is equal to the original ticket summary field (summary field not to be pre-determined in the automation rule)

-Actions- If those match then:

* Transition the duplicate(s) ticket(s) to "resolved/cancel" status
* AND issue field to "resolution" = Duplicate
* AND add comment to issue "Duplicate request"

If anyone has any advice on this it would be greatly appreciated :)

Thanks Jono


Answers:
author: Duc Thang TRAN
body: Hello [@Jonathan Lewis](/t5/user/viewprofilepage/user-id/5352227)

Can you try this one in lookup issue jql part ?

project = "PSP" and issuetype = "Service Request" and status = "Waitting for Support" and resolutiondate is empty and summary \~"\\"{{triggerIssue.summary}}\\""

![Capture d??cran 2024-06-12 084730.png](https://community.atlassian.com/t5/image/serverpage/image-id/329370iE50414FC975CC264/image-size/large?v=v2&px=999 "Capture d??cran 2024-06-12 084730.png")

Normaly, that will cancelled all new ticket with exact same summary

comments: author: Jonathan Lewis
body: Hi [@Duc Thang TRAN](/t5/user/viewprofilepage/user-id/5371199)

Thanks for your response, this one worked perfectly, appreciate your response on this :)

Screenshot to show confirmation on the Audit log:

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


author: Duc Thang TRAN
body: [@Jonathan Lewis](/t5/user/viewprofilepage/user-id/5352227) Glad that helped you :) , in this case you can maked as accepted response


Tags: data-center

jira-service-management

jira-service-management-data-center
Creating a Custom JSM Administrator Role
Asked by Thomas Applebay:

Hello Everyone,

We are currently working to role out JSM, but something that has come up are multiple IT staff wanting admin level permissions to help manage "things". I have come to the conclusion that at most we would want certain people to manage Queues, maybe Automation, but would only want 1-2 admins to manage the rest (Request Types, Workflows, etc.).

Is there a way for me to create a "Sub-Admin" that can only help manage Queues for example? I was not able to find anything outside of Project Roles at the system level.

Additionally, is there a way to stop Agents from being able to run reports? We would prefer if this could be restricted to Administrators only. I was not able to find anything on this either.


Answers:
author: Mikael Sandberg
body: No, you have to be project admin in order to manage automations, request types etc. There is no lower level admin permission that you can give someone to just get access to automations for example.

comments: author: Thomas Applebay
body: That's unfortunate, but expected it from what I was seeing. I appreciate the answer!


Tags: cloud

jira

jira-service-management

jira-service-management-cloud
Unable to select a component
Asked by Vin P:

Hello JSM experts,

As a project admin, I am attempting to create new components for my project. However, when I enter a name (any name, including my own) in the component lead field, no search results appear. In contrast, the JSM admin can search and select the same user's name that I attempted to use.

Could there be access restrictions that prevent me from creating components? If yes, can the restriction be removed by the JSM admin?

Thanks.


Answers:
author: Joseph Chung Yin
body: [@Vin P](/t5/user/viewprofilepage/user-id/5518527)

Welcome to the community. I believe this is caused by the Global Permissions at your site level "**Browse users and groups"** doesn't call out to the user group(s) that you are a member with.

You will need to work with your site admins to update the the global permission configuration listed above to resolve your issue by including the group that you are a member of it.

Hope this helps.

Best, Joseph Chung Yin


Tags: cloud

jira-service-management

jira-service-management-cloud
Comment: For Customers SLA condition not working as expected
Asked by alex_webber:

Hi,

We use a separate platform on top of Jira to respond to our customers but have noticed that this particular SLA condition is only satisfied when the ticket's reporter responds - this is the wrong way around than intended. Instead we want the agent's comment/response going out to the ticket's reporter to satisfy the SLA condition.

How can the latter be achieved here?


Answers:
author: Joseph Chung Yin
body: [@alex_webber](/t5/user/viewprofilepage/user-id/4675615) -

Can you clarify "use a separte platform on top of Jira to respond to our customer" process? Need to understand a bit more, so we can assist you further.

Best, Joseph Chung Yin

comments: author: alex_webber
body: [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739) we use our own product to handle/write responses, however, these are still piped through Jira and logged as comments FWIW.


author: Joseph Chung Yin
body: [@alex_webber](/t5/user/viewprofilepage/user-id/4675615) -

Thanks for your updates. When your custom process adds comments to the customer's issues, are those comments added as "Shared with Customers" opton in the issue? This means that those comments are visible in the portal when customers access his/her issues.

Lastly, who is tagged as the sender of the comments?

Best, Joseph


author: alex_webber
body: Hi Joseph,

**Re. When your custom process adds comments to the customer's issues, are those comments added as "Shared with Customers" opton in the issue?**

Where can we tell if this option is selected?

**Re. who is tagged as the sender of the comments?**

Eliza Wiraatmadja - Gladly on Gladly JIRA Integration


author: Duc Thang TRAN
body: Hello [@alex_webber](/t5/user/viewprofilepage/user-id/4675615)

Can you share you setting of SLA ?

comments: author: alex_webber
body: [@Duc Duc](/t5/user/viewprofilepage/user-id/1460442)

*** ** * ** ***

![Screenshot at Jun 11 13-48-42.png](https://community.atlassian.com/t5/image/serverpage/image-id/329283i44BE721FFF8DEC83/image-size/large?v=v2&px=999 "Screenshot at Jun 11 13-48-42.png")


author: Duc Thang TRAN
body: Hello [@alex_webber](/t5/user/viewprofilepage/user-id/4675615)

In the past, I had an issue with this condition "Comment for Customer" on Data Center. I don't know if it is applicable on Cloud:

When an agent (the same as the reporter or is in the request participant list) makes a comment, the SLA won't stop.

is it the same case for you ?


author: alex_webber
body: I guess I'm confused if Customer implies the Reporter or the Agent in this instance and why there isn't an option for Assignee comments, for example.

As it stands with **Comment: For Customers** added as a condition to satisfy the SLA it seems that this implies the reporter - which makes 0 sense from a support response stand point.


Tags: cloud

jira-service-management

jira-service-management-cloud
Configure custom field "Team" to have multiple sub teams
Asked by Kay:

I want to be able to create different teams within Jira Service Management using the "Team" custom field such that when a customer raises a ticket, the customer can choose which either of Team A or B or C should address the ticket. In the backend, only agents within the selected team should be able to view the tickets e.g if customer choose team A, only agents in team A should see the ticket and respond to it.

Is this possible with Jira service management?


Answers:
author: Mikael Sandberg
body: Yes, that is possible and what you are looking for is called issue security. What you need to do is create a issue security scheme and then use automation to set the security level on the request based on what the customer selected in the Team field. Check out this KB for more information, [Configure issue security schemes](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/).


Tags: cloud

jira-service-management

jira-service-management-cloud
Changing the names of the work categories
Asked by Traci Hawes:

Are we able to change the names of the work categories in Jira Service management or are we only able to use service, incidents, problems, change, etc. Can we either rename these or make new ones?


Answers:
author: J_ Caldwell
body: Currently no you cannot make new ones or change them. The work categories are ultimately tied to set's of functionality/behaviors that you can turn on and off within a project, and are effectively bundled along the lines of the style of ITSM work that will be being done and provides a ITSM style starting point for each of the categories.   

Now....you can through request types/issue types effectively categorize them if that is what you are looking for. Also labels/etc would all be possible.   


Tags: cloud

jira-service-management

jira-service-management-cloud
Limit Customer Request Types By User Group In Jira
Asked by David Harkins:

Is there a way to limit the available Customer Request Types as part of a behaviour?

Trying to to get this working at a basic hardcoded level first

LinkedHashMap optionMap = \[:\]  
optionMap.put("-1", "None")  
getFieldByName('Customer Request Type').setFieldOptions(optionMap)  
But cannot get this to work yet.  
We have been limiting which Issue types can be raised from the blue create button in Jira,  
Now we need to the same for the Request Types, as some should only be raised via the portal.


Answers:
author: David Harkins
body: I managed to get this working in a different way, by means of checking is a user is a Group or Role.  
If they are, and it meets the criteria for that request type, the fields for that request type are set as required. (Visible, Read Only, Form Value, Label, Description).  
if not, all other fields remain hidden and an error is displayed stating the user does not have access to that request type.


author: Ram Kumar Aravindakshan _Adaptavist_
body: Hi [@David Harkins](/t5/user/viewprofilepage/user-id/4150367)

Unfortunately, this is not something that is doable via ScriptRunner's Behaviour.

It's not possible to restrict the Request Types via the Behaviour mainly because the Behaviour only works for Create / Edit / Transition and Assign screens.

The Request Types do not appear on any of these screens for the Behaviour to control it.

Thank you and Kind regards,  
Ram


Tags: behaviours

data-center

jira-service-management

jira-service-management-data-center

scriptrunner