youngmon/atlassian-qna huggingface dataset:
Unable to upgrade Bamboo from 5.7.2 to 6.3.1
Asked by David Weiss:

Windows 2008 R2 SP1. I stop the tomcat service and run the installer for 6.3.1. It runs and completes without error. Open the bamboo home/login page - it still shows version 5.7.2.


Answers:
author: David Weiss
body: This article <https://confluence.atlassian.com/display/BAMBOO0602/Bamboo+upgrade+guide> says you can't upgrade directly using your existing ***install*** folder. Upgrading is really installing the new version to a new folder, and pointing it to ***your existing home directory***. I recommend following the steps there, including the requirement/environment check , or perhaps Atlassian has a better procedure documented.


author: somethingblue
body: Hi David,

I think the best place to start will be the Bamboo logs. See if there was an issue with the upgrade and if it started but perhaps did not complete. If that is the case you should have a reason as to why.

When you find the relevant logs snippets if you need help figuring out what it means please post the snippet here and we'll go from there.

Cheers,

Branden

comments: author: David Weiss
body: Thank you, Branden. I found an article suggesting I backup the machine, stop Bamboo, remove the service, rename the current install directory to OldBamboo, run the install as new but pointing it to the existing Bamboo home, copy the server config XML file from OldBamboo to the new install folder, install the service and start. This got me past this issue but I have other platform/environment issues to work out. I'll post this as an answer.


author: somethingblue
body: Ah. Thanks for the update and what you did to resolve it. If you need help with the additional issues you're running into please post a separate post and we'll answer it there.
Have a dozen trouble with atlassian support
Asked by Nikita Voloshin:

Hi,

at first I can't sent this report because I have a infiti redirect at <https://support.atlassian.com/contact/#/> page

and when I click on 'On line help' I see

Page Not Found

The page you were trying to reach could not be found: it may have been renamed or moved to another space, or the name you requested may be incomplete.

My problem is integrate JIRA and Bamboo I can't see build status in JIRA issue in development section.

in Configure Application Links the status is CONNECTED in both services


Answers:
author: somethingblue
body: Hi Nikita,

There is a knowledge base article titled [Bamboo build information is missing under builds tab in JIRA](https://confluence.atlassian.com/bamkb/bamboo-build-information-is-missing-under-builds-tab-in-jira-653951219.html)that may help:

##### **Cause** {#toc-hId-1200213178}

This issue is caused by XSRF protection settings in Bamboo. Following bug report is addressing this problem. Though it was marked as "Resolved" in Bamboo 5.4 , when Bamboo is integrated with an older version of JIRA, the issue becomes active again: [Enabling the XSRF in Bamboo cause the integration with JIRA 6.1.5 to break](https://jira.atlassian.com/browse/BAM-14129).

#### Resolution {#toc-hId--1155430278}

1. Navigate to Bamboo administration - \> Security settings
2. Uncheck the "Enable XSRF protection" checkbox and save.
3. Refresh both applications. You should now be able to see information from the related Bamboo build showing up under JIRA's "Builds" tab

Try this and let us know if this resolves your issue. If you're using a version higher than 6.1 let us know which version you are running and we'll go from there.

Cheers,

Branden

comments: author: Nikita Voloshin
body: Thank you. It works.

It was a long road to find the form where I had ability write my questions.


Tags: jira
Is there a way to pass arguments to docker build in the Bamboo Docker "Build a Docker image" task?
Asked by Ken:

I can see in the documentation for the Docker task that you can specify environment variables for the "Build a Docker image", but what about arguments to the actual docker build command?

Specifically, I would like to use the "--add-host" argument for my docker build. I'd like to use it at build because I can't use it in my docker run command (I'm running this container outside of Bamboo).

I think I can get around this issue by manipulating my Dockerfile and/or container script to manipulate /etc/hosts directly; but it would be a lot cleaner, IMO, if I had access to the docker-provided option.


Answers:
author: Alexey Chystoprudov
body: There's no such option in Bamboo yet, please vote and comment at <https://jira.atlassian.com/browse/BAM-18797>
How to get all commits linked to a JIRA issue in Bamboo?
Asked by Pieter Wouter Hartog:

I'm developing a Bamboo plugin that scans / searches a SVN repository - I need to collect all commits linked to certain JIRA issues.

Perhaps there's a method to do exactly that, but I have not found it. Instead, I'm collecting ALL commits and scan the comments for the JIRA issue keys.

To get all the [buildChanges](https://docs.atlassian.com/atlassian-bamboo/6.3.2/com/atlassian/bamboo/v2/build/BuildChanges.html)(collection of commits), you can execute

[SvnChangeDetector.collectChangesSinceRevision()](https://docs.atlassian.com/atlassian-bamboo/6.3.2/com/atlassian/bamboo/repository/svn/v2/SvnChangeDetector.html#collectChangesSinceRevision-com.atlassian.bamboo.plan.PlanKey-com.atlassian.bamboo.vcs.configuration.VcsRepositoryData-com.atlassian.bamboo.plan.vcsRevision.PlanVcsRevisionData-)

However, when looking at the source code of this method, it maxes out at 100 commits. In my case, I need to go back further than that.

I tried to extend the [SvnChangeDetector](https://docs.atlassian.com/atlassian-bamboo/6.3.2/com/atlassian/bamboo/repository/svn/v2/SvnChangeDetector.html)class, but there are properties in the super class [AbstactSvnExecutor](https://docs.atlassian.com/atlassian-bamboo/6.3.2/com/atlassian/bamboo/repository/svn/v2/AbstractSvnExecutor.html)that I can't get to, which are needed to make this work. Maybe there's a trick to make this work?

The max of 100 is eventually defined in the interface [SvnConfigurationConstants.MAX_COMMITS_TO_RETURN](https://docs.atlassian.com/atlassian-bamboo/6.3.2/constant-values.html#com.atlassian.bamboo.repository.svn.v2.configurator.SvnConfigurationConstants.MAX_COMMITS_TO_RETURN). I don't think I can access those constants. since constants defined in an interface (static final).

How can I go back more than 100 commits? Or collect all commits for a given JIRA issue?


Answers:
author: somethingblue
body: Hi Pieter,

The 100 items max return is hard coded and at the moment there is no workaround. I believe this is related to [100 build commits limitation cause missing JIRA issues linked to build and limited commits shown when creating release as it relates to](https://jira.atlassian.com/browse/BAM-14145) Bamboo.

The first issue has been closed, however, please vote on the second issue and add your use case to the comments.  

Cheers,

Branden

comments: author: Pieter Wouter Hartog
body: Thanks Branden. I added my vote and a comment with a short use case.


Tags: bamboo-app
Build plan branch specific bamboo java specs settings
Asked by Matthias Kannenberg:

In bamboo build plans I can set at least some options specific for branches like with which plan to auto-merge or clean up settings.

Can I also set these options through java specs? They do not exist in the exported java specs of existing plans.

We have some special branches which exist in all our repositores (for special environments or QA steps) and I would like to avoid setting these up manually for all build plans.


Answers:
author: Alexey Chystoprudov
body: There's no support for Plan branches individual configurations in Bamboo Specs yet. We're going to add them in future versions

comments: author: Matthias Kannenberg
body: Thanks Alexey! Do you have any time frame for when this will be added? I had hoped this would already be coming with 6.4. (as it seemed quite a logical step) but since 6.4. is out now any time frame would be great to have.


author: Alexey Chystoprudov
body: We don't have public timeframe for this feature yet


author: Yogesh Gupta
body: Is it available now?


author: Artsiom_Tverdakhleb
body: [@Alexey Chystoprudov](/t5/user/viewprofilepage/user-id/781646)   
Any updates on this topic?


author: Alexey Chystoprudov
body: Keep watching <https://jira.atlassian.com/browse/BAM-19620>. We're working at this feature


Tags: bamboo-development
need help JQL query
Asked by Kishor Mudhili:

Hi guys,

I want to generate report for below queries using filters.

1. Average time taken to approve the 1st and 2nd approvers. (we have two steps approvals in my project)

2. After Approved average time taken to resolve the ticket meaning how much time taken to given the access

3. From creation to resolved average how time taken to resolve the access tickets.


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

A JQL filter is not going to give you these reports. Al it does, is retrieve a list of issues that you can then report on.

Since you seem to be using JSM, you could leverage SLA's to do your reporting with built-in features.

* define an SLA *Approval time* that you start when the 1st approval is requested and stops when the issue is approved;
* define a *cycle time SLA* that starts when the ticket is approved and stops when the access is given.
* define a *lead time* or *resolution time SLA* that starts when the issue is created and stops when it is resolved.

JSM has built in reports where you can report on the average resolution time. [This support article](https://support.atlassian.com/jira-service-management-cloud/docs/create-a-new-custom-report/) should get you started with how to create your own reports. And [this is a good starting article on setting up an SLA](https://support.atlassian.com/jira-service-management-cloud/docs/create-a-new-sla/). Both articles have links to more detailed information.

Hope this helps!


Tags: cloud

jira-service-management

jira-service-management-cloud
SLA Panel in Context Field is missing
Asked by CyberQ Jira Integration:

Suddenly, the SLA Panel in issue view disappeared. I checked the issue layout and I noticed that the SLA Panel in the Context Fields is not there! How can I add it back? Thanks.

![2024-03-09_19-10-32.png](/t5/image/serverpage/image-id/311151iC65021FB1D0D1776/image-size/large?v=v2&px=999 "2024-03-09_19-10-32.png")![2024-03-09_19-11-06.png](/t5/image/serverpage/image-id/311152i7986BE2BAD3DB6B4/image-size/large?v=v2&px=999 "2024-03-09_19-11-06.png")


Answers:
author: Nabil
body: Hi Jery,

Since we've resolved the issue in the support ticket, I'm sharing the resolution here in case someone else faces the same issue.

We found out that the SLA panel was missing from the Issue View since the SLA panel (system field) was moved to the second tab of the screen configuration. The SLA panel is hard-coded to the default tab and won't work if it's moved to a different tab.

Hope this helps anyone who faces this issue too.

Regards,

Nabil


author: Joseph Chung Yin
body: [@CyberQ Jira Integration](/t5/user/viewprofilepage/user-id/5243307) -

Hi Jery:

For the project in question, did you check if SLA configuration is completed/activated for the project? If not, then you will not see the SLA portion in the issue view.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

comments: author: CyberQ Jira Integration
body: Hi [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739) - yes it is completed and activated for the project. The SLAs (time to first response and time to resolution actually works and can be seen in the queue but not on issue view.

![2024-03-10_16-34-43.png](https://community.atlassian.com/t5/image/serverpage/image-id/311176i9071CAF52B5B0EA3/image-size/large?v=v2&px=999 "2024-03-10_16-34-43.png")![2024-03-10_16-35-58.png](https://community.atlassian.com/t5/image/serverpage/image-id/311177iC66BF4867FE1208C/image-size/large?v=v2&px=999 "2024-03-10_16-35-58.png")

![2024-03-10_16-36-23.png](https://community.atlassian.com/t5/image/serverpage/image-id/311179i0F85155B809B98A5/image-size/large?v=v2&px=999 "2024-03-10_16-36-23.png")


author: Joseph Chung Yin
body: [@CyberQ Jira Integration](/t5/user/viewprofilepage/user-id/5243307) -

It seems very odd. Take a look at this KB article to see if this was your issue - <https://confluence.atlassian.com/jirakb/slas-in-jira-service-management-are-missing-or-disappear-954252774.html>

One possible option for you will be to open those SLA configurations and save them again for the specific project. This will trigger a graceful reindex of SLA against your issues. Afterward, you should see the SLA content in the issue view again. NOTE - the reindexing process does take some times to complete.

Lastly, if not thing works. then you should contact Atlassian Support (<https://support.atlassian.com>) for further assistance.

Best, Joseph


Tags: cloud

jira-service-management

jira-service-management-cloud
Getting an Error Message suddenly on Import into Asset Management within JSM. Error is Generic.
Asked by Tony Anselmo:

When trying to import objects into our Schema Configuration recently, we are getting errors that state: \[Primary Key Object\]; At least one value must be set;

These errors were not occurring about two weeks ago, and now we are unable to import items into the system. Any tips on where or what I can look at to find the specific error? All fields are being provided in the .csv file.


Answers:
author: Fabian Lim
body: Hi [@Tony Anselmo](/t5/user/viewprofilepage/user-id/5226442)

I would check if someone set an attribute on the object to be mandatory after the import. Check your attributes and whatever is mandatory must be imported with a value.

Regards,

Fabian


Tags: cloud

jira-service-management

jira-service-management-cloud
Correct json format for selecting device from the custom field(asset)
Asked by Soobin Kye:

Hi everyone,

I'm working on setting up a webhook alert to create tickets on our customer service portal. When a device encounters a problem, it will send a webhook to Jira, which will then automatically generate a ticket. I can define some information in the webhook payload template (in JSON format), and I would like to incorporate a function that selects the alerting device from a custom field.

Since I have an object schema with assets, I've configured a custom field for it. Initially, I attempted to include the serial number of the alerting device like this:

    "customfield_XXXXX": [ { "name": "{{deviceSerial}}" } ]

However, Jira ignored this field, leaving the custom field empty. On the other hand, when I used:

    "customfield_XXXXX": [ { "objectId": "XXX" } ]

successfully created a ticket with the alerting device selected in the custom field, as I directly specified the asset ID.

I'm looking for guidance on how to adjust the code so that I can update the custom field with the serial number or device name. Since we won't know in advance which device will trigger the alert, I can't simply use a fixed objectId. While I understand that automation is a great option, I would prefer to stick with API calls.

Thanks in advance!


Answers:
author: Sahil Godse
body: Hi [@Soobin Kye](/t5/user/viewprofilepage/user-id/5448521)

We are still facing this issue can you let me know if you have any solution?

Also what is objectId you're sending in 2nd payload


Tags: asset-management

assets

cloud

custom-field

jira-service-management

jira-service-management-cloud
How to automatically duplicate fields from an issue ticket to a new diff ticket type
Asked by Katerina Angjeli:

I need to create an investigation ticket from an existing issue ticket. Many of the fields in the original ticket will remain the same, so I want them to be duplicated automatically in the new ticket. For my application I need to have two distinct tickets for this process. Bottom line I want to prevent errors that could arise from manually entering the information again for the second ticket. This isn't (service desk to jira) it's (jira issue to jira issue) but different issue types.


Answers:
author: John Funk
body: Hi Katerina - Welcome to the Atlassian Community!

You can create an automation rule to do that. You can either have a manual rule that you execute from the initial ticket, or you could have the rule fire automatically when the first ticket is created.

Since I don't know when you want it to be executed, I will go with a manual rule for now.

1. Create an automation rule based on a Manual trigger.

2. Add an action for Clone Issue

You are done.

If you only want to only copy some fields and not all of them, then you can do this.

1. Create an automation rule based on a Manual trigger

2. Add an action for Create Issue

3. Select the fields you to copy over automatically.

4. Next to each field, click the 3 dots and select Copy

5. Click the words Current Issue and change to select from Trigger.

Be sure to save and turn on the rule.

comments: author: Katerina Angjeli
body: Thank you, John!


author: John Funk
body: You are welcome.


Tags: jira-service-desk-data-center

jira-service-management

jira-service-management-data-center
How to isolate between different Service Projects?
Asked by john chen:

Hi,

I have 2 service projects on JSM for customer support. One used for official external customer support and the other one for internal feature testing purposes. When a request is created on the official portal, on Requests tab under the Request type drop down, i can see request types from all of service projects. Is there a way to separate them and only show the Request types defined under that specific service project?

Thanks!

John


Answers:
author: Walter Buggenhout
body: Hi [@john chen](/t5/user/viewprofilepage/user-id/5447776),

That is a permissions matter. Each project has separate permissions that you can define. It's good to have a close look at at least the following support articles:

* [Change service project permissions](https://support.atlassian.com/jira-service-management-cloud/docs/change-service-project-permissions/)
* [Change project customer permissions](https://support.atlassian.com/jira-service-management-cloud/docs/change-project-customer-permissions/)
* [Change access settings for your customers](https://support.atlassian.com/jira-service-management-cloud/docs/change-global-customer-permissions/)
* [How customer access settings impact project permissions](https://support.atlassian.com/jira-service-management-cloud/docs/how-global-permissions-affect-project-permissions/)

Apart from that, when you are an agent (an internal user who works on requests from customers) in both projects, it is entirely normal that you can see request types from both projects in the help center. Just be aware that - when permissions are properly set up - customers will only see the request types from the JSM projects they have access to.

Hope this helps!


author: john chen
body: Thanks for the replies. I basically went to the project that i wanted to hide the request types from and removed permission entirely and its not showning up on my main project. It works for my purpose but it may not be very efficient if you have multiple live projects.


author: Zoey Wang
body: Hi [@john chen](/t5/user/viewprofilepage/user-id/5447776)

If the two service projects are deploying separate request-type schemes

and each Portal has been enabled and visible in your Help Center

and your portal customers can access them respectively, the listed request types should be exclusive to each service project by default.


Tags: cloud

jira-service-management

jira-service-management-cloud
New to community - Need location access to the best docs on OpsGenie
Asked by Paul Hart:

Hi,

In a new role, looking for artifacts about OpsGenie/JIRA and the ability in inviting IT support during P1 calls (automate page out/call in and text acknowledgement).

Sincerely

Paul


Answers:
author: Laurie Sciutti
body: Hi [@Paul Hart](/t5/user/viewprofilepage/user-id/5448482) and welcome to the Community! Here might be a great place to start! <https://support.atlassian.com/opsgenie/>


Tags: cloud

jira-service-management

jira-service-management-cloud

opsgenie
Is there a good way to differentiate tickets submitted via email vs thru the UI?
Asked by Maria DePasquale:

We are enabling ticket submit via email. Once a ticket is submitted via email, I'm not seeing anything that tells me it was an email submit. Ideally, I'd like to auto-assign email-submitted tickets to a special user so they stand out. I had used one of my existing emails and I forwarded it to the jira email acct and the TO acct (the submitting acct) was then in the body of the email. I set up an automation to look for that acct and do an auto-assign which works well. If a user sends a fresh email, I can't find anything for an automation to look for as a differentiator. Has anybody found a way to do this?


Answers:
author: Maria DePasquale
body: I found a solution which is to create an automation that looks for required fields that are empty as they could not be empty if submitted via the UI. This works great.


Tags: email

jira-data-center

jira-service-desk-data-center

jira-service-management-data-center
Upcoming Importer Update
Asked by Joey Bautista:

We got a notice in our cloud instance that Atlassian will be rolling out a change in June that will prevent anyone who isn't an org/site admin from using the bulk importer. This is a wildly disruptive change and essentially destroys the reason we moved to JIRA (we have multiple project owners who need to bulk upload but they shouldn't be org/site admins).

Does anyone know if there will be an option to continue to let standard users to bulk import? Can we opt-out of this "improvement"?


Answers:
author: Fazila Ashraf
body: Hi All,

New update: With the ticket i raised with Atlassian support, this is what they said:

"I have checked internally and I can confirm that the roll out of the depreciation has been postponed till September 2024 until the team will find an alternative for importing CSV files in Jira for non-admins and the notification of this enrolment should soon disappear

So far the CSV Import feature is still available to everyone and on the future you will be notified with the new alternative for importing CSV files in Jira for non-admins."

Phew!!!


author: Ethan Vaughan
body: People in my corpo are also freaked out about this change.

Will this change only change the csv importer? Will who can use the Bulk Edit function still be available to all? There's some confusion about what this update actually changes and who will be affected.


author: John Funk
body: Hi Joey,

Can you share the notice you received?

comments: author: Akeem Williams
body: I saw this message as well and this is what I see:

**We're improving the import experience**

Starting April 2024, we're rolling out an improved importer experience for Site and Org admins. It'll be available to all Site and Org admins by June 30th 2024.

Until then, everyone can continue using the current importer tool. After June, only Site and Org admins will be able to import data.

To move data, you can still use:

* [Bulk Edit feature](https://confluence.atlassian.com/jirasoftwareserver/editing-multiple-issues-at-the-same-time-939938937.html): To edit, update, and/or move multiple issues.
* [Migration Assistant](https://support.atlassian.com/migration/docs/migrate-all-jira-data-at-once-using-the-assistant/) (admins only): To move data from Server to Cloud.

I also want to be able to opt-out of this improvement as it would be wildly disruptive to my organization. I've added feedback around this here as well:

<https://jira.atlassian.com/browse/JWMCLOUD-644>


author: John Funk
body: Thanks for sharing! I have not seen that notice yet.


author: Joey Bautista
body: Yes, the one Akeem posted is the same I got.


author: John Funk
body: I am hearing that this will be pushed out until September and that there will probably not be a restriction to just admins.


Tags: cloud

jira-service-management

jira-service-management-cloud