youngmon/atlassian-qna huggingface dataset:
Can be ZAPI turned on/off?
Asked by Matej Sobota:

Situation overview.

We have JIRA, Bamboo running docker, Zeplin and tests that have ZAPI.

Question:

Can i use some argument in bamboo task that is running these tests to influence ZAPI? Like it will still be in code and everything but it will do nothing if some argument is present. No cycle/execution creation..no step/execution status update etc..

Now we have it in different branch and if i want ZAPI i run branch with and if i do not want i run branch without.


Answers:
author: Daniel Santos
body: Hi [@Matej Sobota](/t5/user/viewprofilepage/user-id/3334497)

I don't use ZAPI or Zeplin, but I'll try to share the information I have to allow you planing your next moves to solve this.

Options I see:  
**Option 1**

* Use a Bamboo plan or injected variable to configure if you want ZAPI to run or not. Assuming you using ZAPI from in a script you could test that variable to decide if the ZAPI part of the script should run or not.
* You can use the option run customized to change the plan variables for a specific run only.

**Option 2**

* Use a Bamboo plan variable to decide what tasks should run or not. This is possible by using the bamboo conditional tasks plugin.  
  You can find more details about this plugin in this thread: [Solved: How we can configure job with conditional tasks for bamboo Plug-in?](https://community.atlassian.com/t5/Bamboo-questions/How-we-can-configure-job-with-conditional-tasks-for-bamboo-Plug/qaq-p/1105461?utm_source=atlcomm&utm_medium=email&utm_campaign=answer_accepted_as_solution&utm_content=topic)

I hope that can shed some light on some options to deal with this challenge.


Tags: docker

zapi
Is it possible to trigger email notification using Bamboo REST API calls?
Asked by Vinod Kumar:

Hi,

I'm using Atlassian Bamboo verison 6.4.1.

I have written a program in NodeJS to trigger deployments using the Bamboo REST API's calls. It is all working and I'm able to do the deployment as well.

Now, I want to trigger the email notification using only the Bamboo REST API's where I can send some custom email body, subject, etc.

Is it possible to trigger the email notification using the REST API's?

Any link or documentation will really help me to complete this task.

Thank you


Answers:
author: Daniel Santos
body: Hi [@Vinod Kumar](/t5/user/viewprofilepage/user-id/3543188)  

It is not possible to send notifications using Bamboo REST API. We have feature requests for this. I see that you commented on one of them:

* [\[BAM-17085\] Send customized email via Bamboo Task](https://jira.atlassian.com/browse/BAM-17085?jql=project%20%3DBamboo%20%20and%20text~%22email%20notification%20rest%20api%22%20order%20by%20createdDate%20)
* [\[BAM-13642\] Add REST API service to send email notifications from Bamboo](https://jira.atlassian.com/browse/BAM-13642?jql=project%20%3DBamboo%20%20and%20text~%22email%20notification%20rest%20api%22%20order%20by%20createdDate%20)

<br />

Possible options:

* Try to send the custom email from within a task using **mutt** . Example of discussion in this thread: [Solved: Bamboo - Send email notifications to list generate...](https://community.atlassian.com/t5/Bamboo-questions/Bamboo-Send-email-notifications-to-list-generated-by-job/qaq-p/1032755?utm_source=atlcomm&utm_medium=email&utm_campaign=answer_accepted_as_solution&utm_content=topic)
* You could try as a workaround using a list of users based on LDAP or another user repository from outside Bamboo. Due to GDPR compliance, I'm afraid new APIs sharing user data will be more restricted.

This is the best I have to share. I hope it helps you move forward.


Tags: email
Version increment for the dll files
Asked by Atul Yadav:

Hello team,

Is there any plugin or parameter in Bamboo through which we can do the version increment of the different files like dlls along with the build.

Regards,

Atul


Answers:
author: Atul Yadav
body: We dug into the issue and found that like the Jenkins, Bamboo doesn't offer any plugin for the version increment for the dll files. Although you can make the script using PowerShell or bash for the version increment. Remember to use proper variables while using Bamboo yaml. We used Bamboo specs for setting up our pipelines.

Here is our script for the reference,

dir -Path $bamboo_build_working_directory -Filter AssemblyInfo.cs -Recurse \| %{$_.FullName} \>\> assemblyfiles.txt  
(Get-Content -Path assemblyfiles.txt) -notmatch "ExternalComponents" -notmatch "ThirdPartyLibraries" \| Out-File assemblyfiles.txt  
$BUILD_NUMBER= "2.1.0.$Env:bamboo_buildNumber"

ForEach ($system in Get-Content "assemblyfiles.txt")  
{

## Replace the variables with the verions values

Get-Content -Path $system \| Select-String -Pattern 'assembly: AssemblyVersion' -CaseSensitive \| Select-String -Pattern '// \\\[assembly: AssemblyVersion' -CaseSensitive -notmatch \> assemblyversion.txt  
Get-Content -Path $system \| Select-String -Pattern 'assembly: AssemblyFileVersion' -CaseSensitive \> assemblyfileversion.txt  
$ASEMBLY_VERSION=Get-Content -Path assemblyversion.txt \|%{"$($_.Split('"')\[01\])"} \| Foreach-Object { $_ -replace "\\s", ""} { $_ -replace "\\\*","123"} \| where-object {$_}  
$ASSEMBLY_FILE_VERSION=Get-Content -Path assemblyfileversion.txt \|%{"$($_.Split('"')\[01\])"} \| Foreach-Object { $_ -replace "\\s", ""} \| where-object {$_}  
$fileNames = Get-ChildItem $system -Recurse \|  
select -expand fullname

foreach ($filename in $filenames)  
{  
( Get-Content $fileName) \| Foreach-Object { $_ -replace "$ASEMBLY_VERSION", "$BUILD_NUMBER" } \| Set-Content $fileName  
( Get-Content $fileName) \| Foreach-Object { $_ -replace "$ASSEMBLY_FILE_VERSION", "$BUILD_NUMBER" } \| Set-Content $fileName  
}
Bamboo PlanName from feature branch
Asked by Marais van Zyl:

Bamboo offers the variable bamboo_planname to see what the name of the plan is that is being built. This works great however when we are building a feature/branch-name branch, the plan name is not the name of the plan anymore, but in fact feature-branch-name.

How can I easily get the plan name or log a bug ticket for Atlassian to fix this?


Answers:
author: Daniel Santos
body: Hi [@Marais van Zyl](/t5/user/viewprofilepage/user-id/3570254)

I was checking our bug report system and found this one: [\[BAM-17810\] shortPlanName contains branch name for plan branches](https://jira.atlassian.com/browse/BAM-17810), released 9 days before this message ([Bamboo Release Notes - 6.10](https://confluence.atlassian.com/bamboo/bamboo-release-notes-671089224.html)).

I'm not sure if we are on the same page, but the problem seems to be with the variable **shortPlanName** not with the **planName.** In case I'm wrong, please share your Bamboo version to allow us to check this.  

In my tests this is what I get in Bamboo 6.9.2 ([Bamboo variables](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html)):

```
|branch \ variable|bamboo.planName                    |bamboo.shortPlanName|
|master(default)  |Project Name - Plan Name           | Plan Name          |
|branch           |Project Name - Plan Name - branch  | branch             |
```

For me, the problem seems to be that short plan name is not returning the plan name, but the branch name.

Please let me know if that makes sense.

comments: author: Marais van Zyl
body: Yes sorry I meant shortPlanName. I'm really delighted to see that Bamboo 6.10 contains a fix for this. It will make things a lot easier going forward!

Thanks for fixing this!


author: Daniel Santos
body: You are welcome!  
I'm glad to be the one delivering this news to you.  
Have a good one!
Bamboo takes time to scan bamboo.yaml on large code
Asked by Atul Yadav:

Hello team, Can you please help me with the query, do Bamboo scans each folder to find the Bamboo.YAML file or it directly searches under the bamboo-specs folder. My code size is 2 GB and whenever I commit any change in the bamboo.YAML, the scan never finishes but when I only have the bamboo-specs folder without the code it finishes in 5-10 seconds. If that is the case then it is a limitation with Bamboo and needs the fix ASAP.

Regards,

Atul


Answers:
author: Atul Yadav
body: The issue has been resolved, In order to fix the issue we followed below steps,

1. Login into the Bamboo server with the admin user

2. Run the below command and rerun the build.

git config --system core.longpaths true


Tags: spec

yaml
Bamboo Deployment Plan With Multiple Docker Images
Asked by Geary Sutterfield:

I need to create a YAML deployment plan for an environment that has multiple tasks, each using a different Docker image and different commands being run in the Docker image. And I'm having trouble determining how to do that.

First, I just want to verify that stages cannot be created in a deployment plan, correct?

If stages can't be used, how can I run different Docker images with different sets of commands in a deployment plan? Let's assume I have an environment named "Preprod" and I want to run some tasks similar to:

* Deploy Application (Docker image #1, commands A, B, C)
* Run Selenium Tests (Docker image #2, command D)
* Run OWasp ZAP Scan (Docker image #3, command E)

Is there a way to do this in a YAML deployment plan?

I suppose I could run these tasks as additional stages in the build plan. And just forget using a deployment plan. Or, I suppose another option would be to create a single, composite Docker image with everything I need and use that single image.

What's the best way to approach this deployment plan in Bamboo?

Would appreciate any insight from those more experienced with Bamboo.

Thanks


Answers:
author: Rafael Pinto Sperafico
body: HI [@Geary Sutterfield](/t5/user/viewprofilepage/user-id/3528331) ,

The best approach in here would be running the tasks as additional stages in the build plan since Deployment Environment do not present the Stages concept.

Alternatively, you could be running Ansible, docker-compose or something you could use to orchestrate the behaviour and commands you have mentioned, calling it as a Script task for simplicity.

Kind regards,  
Rafael


Tags: deployment
list all users or search a single user takes 2-3 minutes
Asked by yche276:

We have a problem when we list all users or search for a user with a surname. it takes 2 -3 minutes. We are using LDAP. there are about 200 users and 15 groups. This porblem only happen with bamboo. our bitbucket server, sonarqube and artifactory are all using the same LDAP sever. They don't have this problem.

steps to reproduce

bamboo -administration -\> security -\> users

the page will take several minutes to be loaded.

Bamboo version 6.4.0 build 60404

inorder to identify the root cause, could you please advise what kind of trouble I should do? Thank you!


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

Your version of Bamboo does not have very good LDAP management if compared with new versions available. In order to build the user list, it does lots of LDAP calls (not a great approach). The time needed to build the data you are trying to get heavily relies on LDAP performance and network due to the high number of calls.

My suggestions:

**If you can upgrade** (best option)

* Upgrade to Bamboo 6.6.x or above and you will have a Bamboo instance with the same features of Jira and Bitbucket on managing LDAP connections.  
  [Bamboo 6.6 Release Notes - Atlassian Documentation](https://confluence.atlassian.com/bamboo/bamboo-6-6-release-notes-952624920.html)  

**If you cannot upgrade**

1. Try to restrict as much as possible the tree search in LDAP by using a more specific value for the following configuration attributes:  
   *baseContext, baseUserNamespace, baseGroupNamespace*
2. Try to reduce the number of users and groups with a more restricted search.
3. Check the time taken for your LDAP to return results with an LDAP search from the server where Bamboo is located using the same parameters configured in *atlassian-user.xml.*

I hope it allows you to troubleshoot this issue.
Remove Jira license from users who have not logged in for more than 1 month
Asked by Edgar Salgado Gallardo:

I need to remove the Jira license from users who have not logged in for more than 1 month. Is it possible to perform this review automatically or do I need to do it manually?

In addition to this, can licenses be removed if they were given by Workgroup and not by User?


Answers:
author: Joseph Chung Yin
body: [@Edgar Salgado Gallardo](/t5/user/viewprofilepage/user-id/5513148) -

Welcome to the community. Based on my knowledge, you will do this manually if you are the Jira system admin to remove the license and the review process is manual by default. In our env, users are managed via AD security group and when he/she is no longer with the company, then they will be removed from the AD security group automatically. Since we sync the users with the AD security group, to control Jira application access, his/her license is then revoke from Jira as they are no longer in the AD security group.

On your second question - What do you mean by "Workgroup"?

Please advise.

Best, Joseph Chung Yin

comments: author: Edgar Salgado Gallardo
body: Good morning, regarding the "working group", what we refer to is the area responsible for providing attention to the issues.

Since we provide the permissions by responsible area and not by user, the question was whether we could withdraw these permissions individually or if they have the license, it is only by unsubscribing them from the AD.


author: Joseph Chung Yin
body: [@Edgar Salgado Gallardo](/t5/user/viewprofilepage/user-id/5513148) -

Thanks for your updates. On the permissions by responsible area and not by user question. it seems it is giving based on the project. So, this can be manage by removing the permission against the responsible area for the project in question. However, it is still a manual operation.

Keep in mind that if a user no longer has access to Jira application (i.e. license is removed), then the permissions by responsible area is a mute point since he/she cannot even access the project anymore since they can longer access the application.

Hope this makes sense.

Best, Joseph


author: Idiyana Binti Ahmad Salim
body: i have similar scenario with Edgar. Besides internal user, we also giving Jira access to external user or client so they will be able to see issues related to their request. Due to this, their login activity might be minimal. usually they wont inform us if they no longer need the access. currently, we need to extract the active user list into csv and filter by last seen column and remove the access for those not login for a certain period. this is too manual for us.


Tags: jira-service-desk-data-center

jira-service-management

jira-service-management-data-center
Set up portal URL to auto-populate a single select custom field
Asked by Eric R Hartway:

I have a single select custom field with a customFieldId of 20300. The field URL is:

* <https://my-company/secure/admin/ConfigureCustomField!default.jspa?customFieldId=20300>

It has two options, "fax" and "empty". Below is the URL for the "fax" selection, which shows a value of 20600:

* [https://my-company/secure/admin/EditCustomFieldOptions!edit.jspa?fieldConfigId=21100\&atl_token=BY2W-VXBM-2C9L-N18N_5c3314fef96ba617e0756ae399ccbf05c040738f_lin\&selectedValue=20600](https://my-company/secure/admin/EditCustomFieldOptions!edit.jspa?fieldConfigId=21100&atl_token=BY2W-VXBM-2C9L-N18N_5c3314fef96ba617e0756ae399ccbf05c040738f_lin&selectedValue=20600)

I am attempting to follow the "**Set up URLs with auto-populated request fields**" instructions on this documentation page:

* <https://confluence.atlassian.com/servicemanagementserver0512/setting-up-request-types-1306298366.html>

According to the page, the pre-set url should look like this in order to pre-fill with the "fax" selection:

* <https://my-company/servicedesk/customer/portal/8/create/398?customfield_20300=20600>

This, however, is not working. Any help on why would be appreciated.


Answers:
author: Eric R Hartway
body: Disregard. It was a browser caching issue. After clearing cache, the auto-population worked as expected.


Tags: jira-service-desk-data-center

jira-service-management

jira-service-management-data-center

jira-service-management-server

server
How to clearly link incidents to their parent change
Asked by Cameron Imming:

We have a regulatory requirement to report on any incident created by a change record. Is there documentation on how this is done?

Ideally, would like to be able to report:  
Change Record, Change Date, Incident Record, Incident Report Date

Thank you


Answers:
author: Mark Higgins
body: Hi Cameron,

May need a few more details, and if I'm about to explain what you already know, then I apologise.

You can link tickets, using the Link option, and then the JQL can show your the columns of the linked issue, but not the details of the linked issue.

![Screenshot 2024-06-11 144337.png](https://community.atlassian.com/t5/image/serverpage/image-id/329043iD58CC5EC4BD3CBF6/image-size/large?v=v2&px=999 "Screenshot 2024-06-11 144337.png")

![Screenshot 2024-06-11 144445.png](https://community.atlassian.com/t5/image/serverpage/image-id/329044i188B2FCF7FB187D2/image-size/large?v=v2&px=999 "Screenshot 2024-06-11 144445.png")

You would need (I believe) to extract both sets of data and then merge the spreadsheets, using something like Vlookup.

In short JQL does not do what you want out of the box.

Mark


Tags: cloud

jira-service-management

jira-service-management-cloud
Correo electronico
Asked by Lucas Silvera:

Buenas, quer?a saber como puedo editar el correo electr?nico que le llega a un soportista cuando se genera un it.

En el correo actual llega informaci?n como quien lo creo el resumen, entre otro. Lo que quiero es agregarle el campo "Organizaci?n" como puedo hacer?


Answers:
author: Nadhila Savira
body: Hi Lucas,

This is Nadhila from JSM. Please allow me to answer in English, since this is our support language within EMEA.

In order to change the email sender for your notifications, you can do the following:

1. Choose **Settings** \> **Projects**.

2. Find the project you want to change the sender address for and select \> **Project settings**.

3. Select **Notifications** from the sidebar.

4. Select the pencil icon to the right of the **Email** address.

5. On the Notification email page, select **Edit** next to the email card.

6. From the **Email** drop-down, choose a custom email address, or use the default Jira cloud email. Alternatively, you may customize the email prefix if you choose to use the default Jira cloud email.

7. Click **Save**.

For the complete information, please see [Configure email notifications](https://support.atlassian.com/jira-cloud-administration/docs/configure-email-notifications/).

Onto the "Organization" field, you can set this field automatically based on the user's email domain. This can be done through an Automation template.

To find said template, please do the following:

* Go to **Project Settings** \> **Automation** \>**Templates** \>Select**Set organization using reporter's email domain**.

For the complete information on this topic, please see [How to add Jira Service Management customers automatically to Organization based on reporter email domain.](https://confluence.atlassian.com/jirakb/how-to-add-jira-service-management-customers-automatically-to-organization-based-on-reporter-email-domain-1142450886.html)


Tags: cloud

confluence

confluence-cloud

jira-service-management

jira-service-management-cloud
Bloqueio de registro de horas mensal
Asked by Barbara Martins:

Utilizamos o Tempo para registros de horas di?rias e contabilizamos todo 1? dia do m?s subsequente.

Gostar?amos de saber se existe uma maneira de bloquear o registro de horas automaticamente no ?ltimo dia do m?s.


Answers:
author: Melo
body: Oi [@Barbara Martins](/t5/user/viewprofilepage/user-id/5332972),

Parece que isso pode ser resolvido utilizando o **Tempo Scheduler**. Essa ferramenta permite configurar agendamentos e fechamento do periodos.

Voc? pode encontrar mais informa??es sobre como configurar essa funcionalidade aqui:

* <https://help.tempo.io/timesheets/latest/configuring-the-scheduler-for-email-reminders-and-#ConfiguringtheSchedulerforemailremindersandperiods-SettheSchedulertoMonthlyClosing(Freezing)Periods>

Espero que isso ajude!

Abra?os,

Melo


Tags: cloud

jira-service-management

jira-service-management-cloud
update does not work for description just like in example
Asked by Tomasz Sabramowicz:

I try to update the issue description field using this EXAMPLE that is in official Atlassian documentation but it gives me error that "update" cannot be used for description.

I try different options but it does now update my description but overwrites it.

Can anyone tell me what is not right here?  

![image.png](/t5/image/serverpage/image-id/327788i670DBE0C44CE771D/image-size/large?v=v2&px=999 "image.png")

if this is official example why it does not work with the "update" statement ?


Answers:
author: Charlie Misonne
body: Hi Tomasz and welcome to the Atlassian community!

I found an old bug report for Jira server/ data center and I think it is applicable for Cloud too. See this comment: [https://jira.atlassian.com/browse/JIRAAUTOSERVER-190?focusedId=2619480\&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2619480](https://jira.atlassian.com/browse/JIRAAUTOSERVER-190?focusedId=2619480&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2619480)

Can you try with this code?

```
    "update": {        "description": [{            "set": "a new description"        }],        "labels": [{                "add": "test-label"        }]    },    "fields": {        "summary": "woohoo! a new summary"    }}
```


author: Kalyan Sattaluri
body: hello [@Tomasz Sabramowicz](/t5/user/viewprofilepage/user-id/5506506)

If you mean this [LINK](https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/) where you got your example, then that link does need updates for certain fields.

Please look at the official API docs: [LINK](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put)

*Especially this blurb* : "Note that the `description`, `environment`, and any `textarea` type custom fields (multi-line text fields) take Atlassian Document Format content."

what this mean is, if you need update description, the JSON to use:

    {    "fields": {        "description": {            "type": "doc",            "version": 1,            "content": [                {                    "type": "paragraph",                    "content": [                        {                            "type": "text",                            "text": "add your description here"                        }                    ]                }            ]        }    }}


Tags: automation

cloud

description

jira-service-management

jira-service-management-cloud

rule