youngmon/atlassian-qna huggingface dataset:
Need help to resolve Vulnerabilities
Asked by jitendrabh:

Hi Team,

I found one critical Vulnerabilities (97610 - Apache Struts 2.3.5 - 2.3.31 / 2.5.x \< 2.5.10.1 Jakarta Multipart Parser RCE) in bamboo application. We tried to download struts2-core-2.5.20 .jar from apache strut site but its not working, even I tried from maven repository but no luck. So need help from this community to resolve my issue.

Application not started with struts2-core-2.5.20.jar file so I have to roll back with old file again to run application properly.

Bamboo : version 5.13.0.1 build 51314

File Location : /opt/atlassian/bamboo/atlassian-bamboo/WEB-INF/lib

File Name : struts2-core-2.5.1-atlassian-10.jar

Need greater version than 2.5.1


Answers:
author: Petr Van??ek
body: Hi,

your version is over EOL so I think you have only two options.

1. Recommended - Upgrade to some newer version to minimal 6.2.5+, because till previous version is also CVE-2017-14589 which is really critical (from my experience someone mining on Bamboo by this vulnereability of Struts
2. Risk - Try solve it with another version, but as you know it's not easy or impossible.

Can you make upgrade?

comments: author: jitendrabh
body: HI Petr,

Thanks for quick reply

I need to check if i can upgrade.

Regards,

Jitendra
Is there a way to avoid shared remote capabilities being inherited in new bamboo agents?
Asked by prasantk:

Hi,

We've an existing on premise bamboo infrastructure with several remote agents. To manage the increasing workload, we had setup some additional remote agents running on cloud. We only want 'docker' as a capability for the new agents and would want to avoid the existing shared remote capabilities on these new agents. The existing shared remote capabilities should be used as-is by the current on premise remote agents. **The problem is that these new agents running on cloud seems to inherit the existing shared remote capabilities when connected to the on premise bamboo master.**

Could you please suggest how we can avoid existing shared remote capabilities being inherited in the new bamboo agents?

Any help or pointers is much appreciated!

Thanks and Regards,

Prasant Kumar


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

The behavior you are experiencing is indeed expected. Shared capabilities will be inherited by every remote agent available.

There is an improvement request to split it into sections specifically to solve a problem that shows up when using multiple OS platforms ([\[BAM-20114\] Shared remote capabilities should have agent type distinction (OSX, Linux, Windows, ...)](https://jira.atlassian.com/browse/BAM-20114)). Maybe adding an extra comment in that feature request describing your scenario would be helpful when our devs start designing this feature.
> Could you please suggest how we can avoid existing shared remote capabilities being inherited in the new bamboo agents?

You will need to remove the shared capabilities that you don't want to in all your remote agents and created them directly on the agents. To create the capabilities you can use the method described in this article: [Configuring remote agent capabilities using bamboo-capabilities.properties](https://confluence.atlassian.com/bamboo/configuring-remote-agent-capabilities-using-bamboo-capabilities-properties-289276849.html).
Disable auto linking of issues to build.
Asked by Steve Marek:

Is it possible to disable issues being automatically linked to a given build in Bamboo but still retain the behavior of manually associating an issue to a build? Thank you.


Answers:
author: Aleksei Tomkeiev
body: Is there any update on this? I need this feature as well. I have some custom builds/plans which I don't want to link with Jira issues.
Bamboo: Writing build trigger
Asked by Jason Jaguar Rivero (TEK SYSTEMS INC):

I would like to write my own trigger.

The idea is to perform some operations upon starting the trigger (such as checking an external DB for some data.

If you have any link to an example that'd be great.

Thank you in advance


Answers:
author: Steffen Opel _Utoolity_
body: You might want to ask such primarily app development oriented questions at the dedicated [Atlassian Developer Community](https://community.developer.atlassian.com/) (and in this case the [Bamboo Development](https://community.developer.atlassian.com/c/bamboo-development) category) - usually you have a better chance to get an answer from anyone currently working with the Atlassian product APIs there (many developers from established app vendors are active on the site and less likely to monitor this user oriented community).

That being said, the [Bamboo developer documentation](Bamboo%20developer documentation) should be your first stop, though it is not exactly well maintained and indeed lacks a tutorial on triggers.

**Example source code**

In such situations I generally try to find an existing app with source code. As a licensee, you can download the Bamboo source code to explore how the built-in triggers work, but the huge code base can be complex to navigate.

A considerably easier path is to check out one of the open source apps provided by Atlassian Labs, for example the [Fail Build Trigger](https://marketplace.atlassian.com/apps/1215235/fail-build-trigger-for-bamboo) - you can find its source code in the [bamboo-failtrigger-plugin](https://bitbucket.org/chystoprudov/bamboo-failtrigger-plugin) Bitbucket repository.

comments: author: Jason Jaguar Rivero (TEK SYSTEMS INC)
body: Thank you very much for your comprehensive answer. Yes, I've been looking into the Bamboo source code but it is huge and time is of the essence.

I'll check out the Fail build Trigger as you suggested.

Again thank you.

Jaguar
Is there a way to block new builds from being submitted on Bamboo when preparing to restart?
Asked by luditic:

We occasionally want to restart our bamboo server for issues like a BAMBOO-GIT-PROXY timeout problem.

What is the best way to restart the bamboo service? If I run 'bin/shutdown.sh', will that immediately terminate the Bamboo app and the Tomcat container? Or will Bamboo block new jobs from starting, let all the existing plans continue to run and then shut down when they're done?


Answers:
author: Steffen Opel _Utoolity_
body: I *think* running 'bin/shutdown.sh' does not provide a way to gracefully block new builds and shutdown once all current builds have finished (not 100% sure though, just my small scale experience). Here's an alternative approach:

You can use the [/server/pause](https://docs.atlassian.com/atlassian-bamboo/REST/6.8.1/#d2e3995) REST API to programmatically block new builds from being started, yet allow current builds to finish. I think the only UI integration that exposes this for Bamboo administrators is the 'Manage apps' section - here's a screenshot after I hit the **'Pause server'** button while builds are running:

![bamboo-pause-server.png](https://community.atlassian.com/t5/image/serverpage/image-id/48651i746A3E673BB4127B/image-dimensions/575x182?v=v2 "bamboo-pause-server.png")


Tags: restart
Bamboo Calender
Asked by Ashish Panwar:

Hi All,

As per requirement , we need to show a Date variable as a calendar in deployment job.

Is it possible to have a variable which can show a calendar and populate time and date variable automatically. I have attached the screenshot for more clarity.

![Screenshot.jpg](/t5/image/serverpage/image-id/48548i6E2FD9141E449445/image-size/large?v=v2&px=999 "Screenshot.jpg")


Answers:
author: Foong
body: Try the solution in <https://community.atlassian.com/t5/Questions/How-to-have-dynamic-variable-in-bamboo/qaq-p/415707#M44363>
We are trying to automate the deployments when a pull request is raised and built successfully
Asked by Nishanthini_Mohan:

We use bitbucket and bamboo in our project. We have test environments where we enable feature branch deployments.

We are trying to automate these feature branch deployments whenever the Pull request is raised in bitbucket. We are enabling "gatekeeper" to "merge and build" when the Pull request is made. But we need are not actually merging the feature branch with the master/develop branch. we need that particular build to trigger a deployment(where a feature branch could be deployed)

Could you help us know how could we enable automated deployments for the feature branches with pull requests.


Answers:
author: Foong
body: Feature request <https://jira.atlassian.com/browse/BAM-14013>

Use Script task to trigger deployment through this [REST API](https://docs.atlassian.com/atlassian-bamboo/REST/6.2.5/#d2e4248)


Tags: deployment
Are there known issues with connecting an instance of Bamboo to multiple instances of JIRA?
Asked by Matt Martin:

Hey there,

* We have two server instances of JIRA and currently a single instance of DC Bamboo.
* Bamboo is already app linked to JIRA instance A
* We would also like Bamboo to be concurrently app linked to JIRA instance B

It definitely seems achievable however, when I was doing a search for whether there are known issues with this, I found an article suggesting that Bamboo requires the connected JIRA instances to have no duplicate project keys.

After checking, we have 20 duplicate project keys in our instances and it's going to be a decently significant hassle to resolve this, as such, I wanted to know if this is a real issue and also, why doesn't Bamboo validate connected instances like the other apps (which seems to be qualification of what instance it wants to talk to first before trying to interact).

Thanks for your help!


Answers:
author: Daniel Santos
body: Hi [@Matt Martin](/t5/user/viewprofilepage/user-id/688061),

**Short answer**

Don't link a Bamboo instance with two different Jira instances.

**Long answer**

Although the linking feature works when Bamboo is connected to two Jira instances, this configuration will create confusion for your team.

As you already noticed from other threads there are some issues here related to projects with the same key.

Let's think in the following example:

* **Jira A** has issues: **AAA-1** , **YYY-1**.
* **Jira B** has issues: **BBB-1** , **YYY-1** , and **YYY-2**.
* Assume **Jira A** is the primary

If you create a commit where the message has the issue "**AAA-1** , **YYY-2** , and **BBB-1**", this is what you will get from Bamboo:

* Will create a link to **AAA-1** (**Jira A**).
* Will create a broken link to **YYY-2** (**Jira A** ) - It knows the project **YYY** exists in **Jira A** and therefore creates the link even if the issue is not present.
* Will create a link to **BBB-1** (**Jira B**).

From Jira A you will see:

* The issue **AAA-1** will have a build associated with it

From Jira B you will see:

* The issue **BBB-1** will have a build associated with it.
* The issue **YYY-2** will have a build associated with it (which you will probably not expect). Jira is able to see that there is a build with that key and it shows it.

The example above is just to confirm that if you want this configuration you should never have the same project key in both Jira instances. As you know this is not an easy task and may create some confusion. I believe the best approach here is to have two distinct Bamboo instances, one connected to each Jira.

To provide the information above I've run some tests on Bamboo 6.8.x connected to Jira 8.0.x.

This is one issue already open to reporting improvements in this area: [\[BAM-18727\] Improve the way we generate links between Jira issues and build results.](https://jira.atlassian.com/browse/BAM-18727)

I hope that helps to clarify this scenario.


Tags: application-link

jira

jira-server

server
What does CF-StatsUnavailable (200002) mean?
Asked by Jill Lopez:

Hi,

I'm failing in one of my deployments and I'm getting this error:

Unable to push app with a blue/green deployment: CF-StatsUnavailable(200002): Stats unavailable: Stats server temporarily unavailable.

Does anyone know what this means?

Thanks!


Answers:
author: Steffen Opel _Utoolity_
body: Assuming you are using the [Cloud Foundry for Bamboo](https://marketplace.atlassian.com/apps/1211255/cloud-foundry-for-bamboo) app, I've added the resp. app tag to the question so that the app's author might take note and weigh in.

That being said, there is a matching issue for the [Java Client Library for Cloud Foundry](https://github.com/cloudfoundry/cf-java-client), which the app happens to use:

* [CF-StatsUnavailable(200002): Stats unavailable: Stats server temporarily unavailable (#846)](https://github.com/cloudfoundry/cf-java-client/issues/846)

According to the maintainer's response, *"* *if you see this error it means your system is misconfigured"*, more specifically:
> \[...\] the error message you're getting generally means that there is something wrong with your cloud foundry configuration (though it could just be a transient networking glitch, for example). So you should take steps to try to identify and fix what's wrong.

Accordingly, you might want to recheck whether you can reach the server as currently specified in your Cloud Foundry configuration, maybe there has been an intermittent or permanent change in the network you are using?


Tags: addon-org.gaptap.bamboo.cloudfoundry.cloudfoundry-plugin

deployment
help on JQL
Asked by Kishor Mudhili:

![Capture.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/322685i3FD82CE456634A71/image-size/large?v=v2&px=999 "Capture.PNG")


Answers:
author: Ankit Srivastava
body: Hi [@Kishor Mudhili](/t5/user/viewprofilepage/user-id/5310742),  

Greetings of the day!  

As per my knowledge, it is not possible to fetch the data before and after details field.  
but you may search by:  

Refer the below JQL to fetch the issues which having value in details field. and check all the updated on the ticket itself or for more detailed way you may check the **History/All** under Activity.

*** ** * ** ***

Project = Project Name and details field is not Empty

*** ** * ** ***

<br />

<br />

<br />

Below JQL fetch the issues which doesn't have any value in details field.

*** ** * ** ***

Project = Project Name and details field is Empty

*** ** * ** ***

and same you will check the **History/All** under Activity for brief details.  

Hope this will help.  

Thanks.


author: Mikael Sandberg
body: No, JQL does not have a feature that allows you to capture data between text, this is only possible in automation and [smart values](https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#substringBetween-String-open--String-close-).


Tags: cloud

jira-service-management

jira-service-management-cloud
Request Types related to selected Issue Type Only
Asked by Vijay Dadi:

Hello There !

When I am in Jira Service Management screen and click on Create Issue, if I select Issue Type as Incident, it should show only Request Types in the drop which create Incidents. But as of now the drop down list for Request Types shows all the available request types.

Is there a way to achieve this functionality.

TIA

Vijay


Answers:
author: Asmath Basha S
body: Hi [@Vijay Dadi](/t5/user/viewprofilepage/user-id/5408989) ,

* In JSM Cloud Portal while raising a ticket it will show all the Request types in the dropdown which is available was configured in the service project.
* I think it is a default one.

comments: author: Vijay Dadi
body: That is true, my requirement is while creating a request from JSM Agent screen.

I want only the request types of select issue type to be shown. Is there a way we can achieve it.


Tags: cloud

issue-create

issue-type

jira-service-management

jira-service-management-cloud

request-type
"Add internal note / Reply to customer" not shown
Asked by Olivier B.:

Hi,

I have a JSM project with 3 types of tickets. For one of them, the "Add internal note / Reply to customer" is not visible when a ticket is created :

![Capture d'?cran 2024-05-08 160956.png](https://community.atlassian.com/t5/image/serverpage/image-id/322658i93EA27AD629C2B2F/image-size/large?v=v2&px=999 "Capture d'?cran 2024-05-08 160956.png")

The comment field is only available in the main view after the first transition (where the Comment field is on the transition screen).

I verified : Issue type / request type / Field configuration / Workflow : everything seems to be the same for all tickets...

I'm being mad, thanks for your help !!

O.


Answers:
author: Fazila Ashraf
body: Hi [@Olivier B_](/t5/user/viewprofilepage/user-id/5365263)

hmm interesting.. May be there is a workflow property on the initial status and it is conditionally restricting comment only for this issue type?

comments: author: Olivier B.
body: Yep, that's it !

Now, I need to remember why I've done this... :-)

Thanks !


Tags: cloud

jira-service-management

jira-service-management-cloud
Is there a way to hide the Issue Type
Asked by Vijay Dadi:

Hello,

In Jira Service Management, we are not using Post Incident Issue Type. Is there a way we can hide or disable the issue type on portal and create issue screen.

TIA

Vijay


Answers:
author: Mikael Sandberg
body: Yes, all you have to do is go to Project settings \> Issue types and from here click Actions \> Edit issue types. On the next screen you can move the issue type from the left column ( issue types available to the project) to the right column and then click save.

comments: author: Vijay Dadi
body: [@Mikael Sandberg](/t5/user/viewprofilepage/user-id/853579) this is what i was looking for. Thank you.

Vijay


author: Jack Brickey
body: this works well if there are no existing issues with that issue type. if there are you will be prompted to change the issuetype.


author: Vijay Dadi
body: True, luckily I didn't had any existing issues for that issue type. We are still in the build phase, hasn't gone live yet.


author: Jack Brickey
body: lucky indeed!

I would love it if they had a hide option similar to how you can hide (disable) previously used values in a dropdown custom field. this allows you to retain the history but prevent unwanted ongoing usage.


author: Vijay Dadi
body: But that usually happens when you are trying to delete it but not while disabling it.


author: Jack Brickey
body: [@Vijay Dadi](/t5/user/viewprofilepage/user-id/5408989) , not sure, I understand. ?


author: Fazila Ashraf
body: Hi [@Vijay Dadi](/t5/user/viewprofilepage/user-id/5408989)

If the project is not going to use it, does it make sense to remove it from the project configuration altogether?

If you want to retain existing issues with the same type, you could archive them if you are on premium or may be they could be moved to a different project?

comments: author: Vijay Dadi
body: Hello [@Fazila Ashraf](/t5/user/viewprofilepage/user-id/538419)

Yes, we are on premium version. Deleting it is one option. I am eager to know if there is a option for hiding/disabling it.

Vijay


Tags: cloud

issue-type

jira-service-management

jira-service-management-cloud
No apparent setting to enable Critical Alerts in Jira Cloud for iOS
Asked by optop:

I'm trying to test out Jira Service Management to see if it is capable of sending alerts for our business via the Alerts functionality for a 24/7 on-call team.

I've figured out how to create a Service Project, can see the Alerts and have generated some test alerts.

However even for a P1 alert, I can't find a setting so that a Push Notification will trigger an iOS Critical Alert, only a normal Immediate delivery Push Notification that would be silenced by iOS Do-not-disturb and not make a sound if the volume is down.

All the support documentation around iOS critical alert management is for OpsGenie, however I understand this is all now operating through JIRA Cloud.

Am I missing a settings page in the cloud UI or on my mobile app? Is this a premium only feature for JSM?

Thanks!

Alert settings in JIRA profile:

![Screenshot 2024-05-08 at 15.03.32.png](/t5/image/serverpage/image-id/322654iA1DEA0F775783B66/image-size/large?v=v2&px=999 "Screenshot 2024-05-08 at 15.03.32.png")JIRA Cloud mobile app settings:

![File (1).jpg](/t5/image/serverpage/image-id/322657i4B0790A7E7C945E0/image-dimensions/229x388?v=v2 "File (1).jpg")

Resulting alert:

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


Answers:
author: Ross McCardal
body: This functionality is a must-have for us also if we are to migrate to the new workflows.


Tags: cloud

jira-service-management

jira-service-management-cloud
Report - unrealized issue from the previous day
Asked by S?awomir Ja?oszy?ski:

Hi,

I would like to create a report that will show me how many issues were moved from one day to the next. I would like to easily verify the number of issues that are not resolved on the day of creation, taking into account only one issue type. By default, the created - resolved report is provided, but I would like to see a list of events that we have not resolved and easily review them.  

Greatings  
Slawek


Answers:
author: Walter Buggenhout
body: Hi [@S?awomir Ja?oszy?ski](/t5/user/viewprofilepage/user-id/5413215),

How do you interpret *"move from one day to the next"*?

Reading between the lines, it seems as if you are trying to resolve all issues that were created the same day.

One thing you could do is create a filter with issues created yesterday:

```
created >= startOfDay(-1) AND created <= endOfDay(-1)
```

Using a pie chart gadget on a dashboard, you can then display them by resolution, thus separating the ones that were resolved from the ones that are still open.

A different approach - since you are using JSM - would be leveraging your SLA configuration. By defining a time to resolution SLA that matches the desired time for you people to complete tickets will also allow you to create reports of tickets resolved within or outside the desired target. That may even be a better solution, since it will display the evolution over time instead of just a report on the tickets created on the previous day.

Hope this helps!

comments: author: Vijay Dadi
body: [@S?awomir Ja?oszy?ski](/t5/user/viewprofilepage/user-id/5413215) , I tried this and it worked foe me.

Thank you [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225)


author: S?awomir Ja?oszy?ski
body: [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225)   
Everything works perfectly and the above filter worked properly.  
Of course, I use pre-set SLA schedules that clearly show overdue orders. However, I wanted to know the scale of tasks that are not performed by individual departments in the company. Thank you for your help.


Tags: cloud

jira-service-management

jira-service-management-cloud
I cannot find Roadmap on my project settings- features.
Asked by Irina Poghosyan:

I want to enable Roadmap on my Jira dashboard which is a Software project and I dont have Roadmap as a feature on settings. How can I enable it? ![Screenshot 2024-05-08 at 12.47.25.png](/t5/image/serverpage/image-id/322613i47F5BF7A53753FA2/image-size/large?v=v2&px=999 "Screenshot 2024-05-08 at 12.47.25.png")


Answers:
author: Fazila Ashraf
body: Hi [@Irina Poghosyan](/t5/user/viewprofilepage/user-id/5476162)

Welcome to community!

On a standard plan, Timeline is the same Roadmap

Also read <https://community.atlassian.com/t5/Jira-articles/New-name-same-powerful-features-Roadmap-is-now-Timeline/ba-p/2348378>


Tags: cloud

jira-service-management

jira-service-management-cloud