youngmon/atlassian-qna huggingface dataset:
What sort of data is available for the deployment email templates?
Asked by Chris:

I'm trying to customize the deployment email templates, but i can't find good documentation to acomplish this. All documentation seems to be around Build Templates. Is there any documentation on was sort of metadata/variables are available for deployment templates?


Answers:
author: Steffen Opel _Utoolity_
body: I'm assuming you are referring to [Modifying notification templates](https://confluence.atlassian.com/bamboo/modifying-notification-templates-289276982.html)?!

IIRC, similar to how the Freemarker ${buildSummary} variable basically exposes the resp. Java API [BuildResultsSummary](https://docs.atlassian.com/atlassian-bamboo/latest/com/atlassian/bamboo/resultsummary/BuildResultsSummary.html) interface, the ${deploymentResult} variable basically exposes the resp. Java API [DeploymentResult](https://docs.atlassian.com/atlassian-bamboo/latest/com/atlassian/bamboo/deployments/results/DeploymentResult.html) interface.

You can see this in action within Carolyn van Slyck's [Bamboo Deployment Notifications](https://bitbucket.org/carolynvs/bamboo-deployment-notifications), e.g. in template [EmailSubject.ftl](https://bitbucket.org/carolynvs/bamboo-deployment-notifications/src/b6283c638d65a6a3d82a8dffc2d0ffda0597f098/src/main/resources/templates/MultipleFailedDeployments/EmailSubject.ftl?at=master&fileviewer=file-view-default):

```
[#-- @ftlvariable name="deploymentResult" type="com.atlassian.bamboo.deployments.results.DeploymentResult" --]
[#-- @ftlvariable name="deploymentProject" type="com.atlassian.bamboo.deployments.projects.DeploymentProject" --]
[#-- @ftlvariable name="numFailures" type="Integer" --]
[#assign deployment=deploymentProject.name /]
[#assign release=deploymentResult.deploymentVersion.name /]
[#assign environment=deploymentResult.environment.name /]
${deployment} ${release}[#t]
[#if deploymentResult.deploymentState == "Successful"] was successfully deployed to ${environment} after ${numFailures} [#if numFailures = 1]failure[#else]failures[/#if].[#rt]
[#elseif deploymentResult.deploymentState == "Failed"] failed deploying to ${environment} (${numFailures} [#if numFailures = 1]times[#else]times[/#if]).[#rt]
[#else] stopped deploying to ${environment}[#rt]
[/#if]
```

For a Bamboo version x.y.z installation, you can inspect the built in Freemarker deployment notification templates within the following artifact (search for *\*.ftl*):

*\<bamboo-install\>/atlassian-bamboo/WEB-INF/lib/atlassian-bamboo-deployments-x.y.z.jar*


Tags: deployment

template
Bamboo support for Mainframe
Asked by venkata bandi:

Hi,

We're planning to implement devops for Mainframe system. I don't see the information of Bamboo support for Mainframe online. Could you please let me know the feasibility of Bamboo tool with respective to Mainframe system.

Thanks,

Sreenath.


Answers:
author: Alexey Chystoprudov
body: What kind of support do you need from Bamboo for Mainframe system?

Bamboo can execute any scripts or commands you use in your daily devops activities.

comments: author: venkata bandi
body: My question is, when I see the documentation of JENKINS, I see there is a plugin for zOS but I don't see anything related to Mainframe on Bamboo. So I would like to know whether we can use Bamboo for implementing Devops for Mainframe systems.


author: Alexey Chystoprudov
body: I don't know what Jenkins plugin does, but I'm sure there is no public Bamboo plugin for zOS integration.
Can you modify Atlassian Assist notifications?
Asked by Arlene.Amaya:

Agents are only receiving a notification on Teams (through the Activity icon in upper left hand corner) when a customer creates a new ticket. Is it possible to add notifications for other reasons, such as a customer commenting on a ticket?


Answers:
author: Garvin Tarr
body: I am having a similar issue, though it used to work.

Our agents receive notification in Teams when issues are created and we used to see notifications when issues were updated. In the past 10 days or so we do not get notifications in Teams upon ticket updates, however we are still notified upon creation. The updates are added to the Teams conversation, however notification of these updates are not working. We had recently migrated from Halp to JSM without any issues. All other Teams notifications still work, so I'm not sure if something has changed with Teams or JSM.

Any thoughts out there?

comments: author: Mark Avery
body: I am experiencing the same issue as well. We receive the notification when an issue is created and posted into the channel for first time but we do not receive any type of notification then the ticket post is edited/updated. Need this working. Does this have anything to do with the new Teams client vs old Teams client or has this worked before in the new Teams?


Tags: cloud

jira-service-management

jira-service-management-cloud
Can you add two components to the field in a post function
Asked by Ron Campbell:

While working on a transition I want to use a post function to figure out two different component values that I want to add to the component field at the same time. One part is where I look at specific answers in the form and add that component. After that the post function looks for a region and adds that component to the field as well. This errors out when I tried to put it as an arraylist return. Any thoughts?


Answers:
author: Kalyan Sattaluri
body: Are you trying this through automation or through your own script?

Please review:

<https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/>

If you are passing it as below, it will not work.

"components" : \[ { "Active Directory"} , { "Network Switch" } \]

You need to pass it as below:

"components" : \[ { "name": "Active Directory"} , { "name": "Network Switch" } \]


Tags: jira-service-desk-cloud

jira-service-management

jira-service-management-cloud

jira-service-management-server
Project configuration errors while setting up JSM
Asked by Robert Cuyugan:

I am setting up JSM and it keeps popping up configurations errors on what appears to be portal group forms that have been hidden as they're aren't intended to be used but it keeps prompting the error to assign a default assignee. Is this mandatory or can be bypassed?

*** ** * ** ***

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


Answers:
author: Bryan Trummer - ReleaseTEAM
body: Hello [@Robert Cuyugan](/t5/user/viewprofilepage/user-id/3011126)

If you don't plan on having the Assignee set to a preset value when its hidden, then you can either unhide that field, or you can just remove Assignee from the Request in general. Either of those options should remove the error message you are seeing.

comments: author: Robert Cuyugan
body: Hi Bryan,

Thank you! What's weird is that it is showing Assignee as Hidden but I don't see it being hidden on any associated screen. So not sure where it's pulling that setting from. Additionally, it shows a message that the field cannot be removed from the request when I try to remove that field from the request.  

Would it cause problems if I delete those request forms instead from the project instead of hiding them? I am assuming they can be recreated?


author: Bryan Trummer - ReleaseTEAM
body: Hi [@Robert Cuyugan](/t5/user/viewprofilepage/user-id/3011126) - Deleting the request forms would not cause any issues, like you mentioned you would have to recreate the request forms again.

Maybe before deleting the request forms, I would verify that you don't have assignee marked as required on the request form, might also be worth checking that in the field configuration as well.


author: Robert Cuyugan
body: How can I check if assignee is required on the form? If I look at the Field configuration it's Required only and cannot be changed and it's associated to a bunch of other screens we use.


Tags: cloud

jira-service-management

jira-service-management-cloud
User dont see the tickets where is participant
Asked by Carlos Rivera:

Hello,

I have a user who appears in the administration in status "Invited". This user have activity, can open tickets since 2021.

I created a new jira service management project, created a new group to add users and this user, can't see the tickets where is participant and other user yes.

Can anyone help me?

Regards


Answers:
author: Asha Goyal
body: Hello [@Carlos Rivera](/t5/user/viewprofilepage/user-id/4488349)

Please make sure that User/Group/Role is added into browse project permission.

Kindly Accept and Vote if it helps.

Thanks

comments: author: Carlos Rivera
body: Hello, AG

Thanks for your soon answer. In browse project permission, apart from other roles, i have "Service Project Customer - Portal Access", i understand that this permission allow users to view this tickets. Is it correctly?

Yesterday i was check the problem and i think that saw the solution. The customer request type field was empty, after assigning content to that field, the user was able to view the ticket.

Regards


Tags: cloud

jira-service-management

jira-service-management-cloud
When closing a ticket, is there a lifespan until it's no longer accessible?
Asked by Michael Jennings-Diaz:

More general if anything. I'm curious how long closed tickets are "archived" for future reference an tracking.


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

There's no lifespan. Issues only get archived or removed when a human deliberately chooses to do it. Albeit some of us script or automate it!


Tags: cloud

jira-service-management

jira-service-management-cloud
Why do fields populate in another Request Type's Issue View when added to another?
Asked by Patryk Mucha:

I have a Jira Service Management project that captures various processes through quite a few Request Types. The issue I am having is that when I create and add fields to a Request Type, those fields are added to the issue view of other Request Types in the project. Is there a reason for this, or a way to prevent it from happening?


Answers:
author: Asha Goyal
body: Hello [@Patryk Mucha](/t5/user/viewprofilepage/user-id/5235712)

Adding a field to a screen will make it appear in the **Issue view**for all request types that share the same issue type.

You'll need to manually remove the field from any request types where it's not required.

Please Accept and Vote my answer if it helps.

Thanks


Tags: cloud

jira-service-management

jira-service-management-cloud
Customer Portal adding external widget
Asked by Luciana Dimauro:

Hi, we are evaluating to purchase some Atlassian products among which Service Desk.

I need to know if it is possible to add an external url as a widget into the Portal. I'll explain: we actually use a chatbot (external) to answer some customer's requests and we would use this chatbot into Jira Service Desk Portal.

How to do that? Where can I read documentation?

For now we are using the free plan but we should purchase the standard one

Thanks

Regards,

Luciana


Answers:
author: Dan Breyen
body: Hi [@Luciana Dimauro](/t5/user/viewprofilepage/user-id/5229165) the JSM Premium and Enterprise have a ChatBot built into the system to assist with answering customer questions. If that isn't an option for you, you can add an external link on the Portal page to your chatbot.

You can reference [this article](https://support.atlassian.com/jira-service-management-cloud/docs/add-links-to-external-resources-in-your-portal/) for steps to add the external link to the portal.

Hope that help.

comments: author: Luciana Dimauro
body: Got it!

Thank you very much

Luciana


Tags: cloud

jira-service-management

jira-service-management-cloud
Change the default priority of a single project in Jira SM (Cloud)
Asked by Ivo Stoyanov:

Hello,

When our customers submit tickets, they usually don't touch the priority and it is automatically set to Medium.

Is there a way to change it to anything else only for the current project?


Answers:
author: Valerie Knapp
body: Hi [@Ivo Stoyanov](/t5/user/viewprofilepage/user-id/5360109) , welcome to the community and thanks for your question.

Unfortunately, in the cloud, not yet having a priority scheme at the project level, you wouldn't be able to change the priorities configuration for a single project.

You could, however, make an automation for this, that sets the priority to low, when the ticket is opened, which can then of course be modified after the ticket has been triaged if it is deemed to be of higher priority. Would that work for your requirement?

comments: author: Ivo Stoyanov
body: Thank you. We've created an automation.


Tags: cloud

jira-service-management

jira-service-management-cloud

priority

project-management
Resposta ao chamado aberto via e-mail
Asked by Izabela:

Meu cliente abriu um chamado via e-mail mas quando respondo a resposta n?o chega para ele via e-mail, como fa?o pra manter contato com o cliente durante o andamento do chamado?


Answers:
author: Jack Brickey
body: *hi [@Izabela](/t5/user/viewprofilepage/user-id/5270184) ,*

Certifique-se de que o rep?rter esteja definido para o nome do seu cliente e, mais importante, certifique-se de que o tipo de solicita??o esteja definido.


Tags: cloud

jira-service-management

jira-service-management-cloud
Portal settings
Asked by Drew Montagna:

Hello,

I've noticed some projects do not have a 'Portal Setting' option.

Can someone explain what type of project needs to be created to utilize this option?

Kanban? Scrum? JSM? Service Management? Company Based? Team Based?

Thanks.


Answers:
author: Nic Brough -Adaptavist-
body: Hi Drew,

Portals are a function of JSM, and are a part of every JSM project. Software, product discovery, and work management projects do not have portals.


author: Jack Brickey
body: Portals are associated with JSM only.


Tags: cloud

jira-service-management

jira-service-management-cloud
Log monitoring on JSM Cloud
Asked by Lukasz Grobelny:

Hello,

Is it possible to monitor logs in JSM Cloud and perform actions based on them? For example, if there is an error, a ticket will be created?

Like adding JSM as a source to OpsGenie


Answers:
author: Dirk Ronsmans
body: [@Lukasz Grobelny](/t5/user/viewprofilepage/user-id/4230826) ,

Short answer, ++No++

You don't have access to any system logs on your Jira Cloud instance.

I'm curious what your use case would be as you also won't be able to do anything about them really if there is a an error in the logs.

What type of errors are you looking to monitor?

comments: author: Lukasz Grobelny
body: We have an Audit log, nothing special there. It's more of a general question - I know we can't do much, but I was just wondering what information if any can be captured.


author: Dirk Ronsmans
body: Nothing really. These are all internal logs monitored by Atlassian.

If they notice anything that will pop up on <https://status.atlassian.com/>


author: Jack Brickey
body: Are you referring to the email logs? There currently isn't a means of doing this.


Tags: cloud

jira-service-management

jira-service-management-cloud
New issue attach form position in issue type view
Asked by Ian Robinson:

Hi folks,

Setting up a new JSM project. We have the customer portal, where a form is used to raise a request.

When the issue is raised, the user view within Jira does not look good. The form is moved to the bottom of the issue view. I know if NO form is used when the customer raises, the contents could be expanded in the 'NAME raised the request via Portal'

I can't find a way to move the attached form up in the page to be one of the first visible since our users will be using that form of information to work from.

Any suggestions?

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


Answers:
author: Zoey Wang
body: Hi [@Ian Robinson](/t5/user/viewprofilepage/user-id/5277555)

If the fields do not necessarily need to be shown as they appear in the screenshot, just hide or remove them as needed. The form at the bottom will be able to move up.

![Screenshot at Feb 18 21-47-46.png](https://community.atlassian.com/t5/image/serverpage/image-id/307083iF88B5E177A2928A2/image-size/large?v=v2&px=999 "Screenshot at Feb 18 21-47-46.png")

comments: author: Shawn Giese
body: Where can we set such options?

Strange the content of a form... which is quite important for a ticket is buried so low and not expanded.


Tags: cloud

jira-service-management

jira-service-management-cloud
Make a custom field mandatory for just ONE request type.
Asked by Ellie Eleana Deisinger:

Im slowly getting frustrated. :/

I've set up a Service Desk with different request types, and some custom fields of which some are mandatory e.g **Location**.

I now created another request type where **Location** is **not** needed.

But i can't get rid of it.

Tried a few "solutions" that where posted here in the community, but they all seem to old, and don't work.

So my question is:

How can i make a field mandatory for just **one** request type?

*Jira really is a complicated setup maze imho, seems really over-complicated for some certain stuff. and we're using it for 3 years now.*


Answers:
author: Vishal
body: Hi [@Ellie Eleana Deisinger](/t5/user/viewprofilepage/user-id/5430524)

Just go to Project Settings \> Request Types \> Click on the request type in which you want to make field mandatory \& then on the field \& you shall find a check box to make field mandatory, like below.

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


author: Rilwan Ahmed
body: Hi [@Ellie Eleana Deisinger](/t5/user/viewprofilepage/user-id/5430524) ,

Welcome to the community !!

Go to your project settings --\> Fields   
Copy the name of the field configuration.  
Go to Jira admin settings --\> Issues --\>Field configuration --\> Click "Configure" against the required field configuration

Search for **Location** field. if the field is marked "Required", then click "Optional" link  
![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/306610iEBB3BA7A7E6412EC/image-size/large?v=v2&px=999 "image.png")

Now add and check the field in JSM project request type. It should not display as required.

If still it is displayed as required, remove field and add back **OR** expand field and **uncheck** "Required" in Request type.  
![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/306612iA7C53F73DDCA5B36/image-dimensions/225x127?v=v2 "image.png")


author: Kai Becker
body: [@Ellie Eleana Deisinger](/t5/user/viewprofilepage/user-id/5430524)

where did you set the field as required?   
If you set it inside the request type configuration you should be able to make it optional for any other request type, like [@Vishal](/t5/user/viewprofilepage/user-id/3505998) wrote.

If you set it required via the field configuration, then it will be required for alle issue types and request types.

comments: author: Ellie Eleana Deisinger
body: I indeed did it via the field configuration, seems like i was blind.

I haven't seen the checkbox [@Vishal](/t5/user/viewprofilepage/user-id/3505998) mentioned. :'D


author: Kai Becker
body: Perfect. Glad that we found the issue. Please don't forget to accept an answer, if you question is resolved.


author: Sathish Kumar Golla
body: Hi,

You can do the below

Project Settings \> Request Types \> Click on the request type

With the help of Adaptive Scriptrunner using Behaviours you can choose the JSM project and update the request type.


Tags: cloud

jira-service-management

jira-service-management-cloud
Workfow settings
Asked by Cansu Genc:

We want to add a "Scheduled" status to the workflow in Jira Work Management and ensure that SLAs do not run when a ticket is set to "Scheduled." Could you please explain the steps we need to follow?


Answers:
author: GNarsimhagowda - Empyra
body: Hi [@Cansu Genc](/t5/user/viewprofilepage/user-id/4785512) ,

Go to the required workflow and simply add the status you want.

To configure the SLA go to project settings and SLA setting and you will have the option to pause SLA when an issue enters certain status and resume when it exits and there are other options as well.

For reference i have added this link in how to configure SLA : <https://support.atlassian.com/jira-service-management-cloud/docs/create-service-level-agreements-slas/>

Thanks.


author: Evgenii
body: Hi, [@Cansu Genc](/t5/user/viewprofilepage/user-id/4785512)

You can make it by editing SLA conditions. It's in Project Settings, SLAs. Looks like:  
++*<https://your_domain.atlassian.net/jira/servicedesk/projects/DEMO/settings/sla/custom/1/edit>*++

++*In your case id of SLA can be other. Each SLA has its own ID*++

There is block with name: ++*Pause counting time during...*++  
Select there status, which you want to use for pausing SLA.  
It will look like:  
![Screenshot_23.png](https://community.atlassian.com/t5/image/serverpage/image-id/306605i0D7DA58CA14ADC16/image-size/large?v=v2&px=999 "Screenshot_23.png")  
In my example I used Pending status to stop SLA count.


author: Tansu Akdeniz
body: Hi [@Cansu Genc](/t5/user/viewprofilepage/user-id/4785512)

First, go to workflow and add new status

* [Add new status and steps to workflow](https://confluence.atlassian.com/jirakb/add-new-status-and-steps-to-jira-server-workflows-718835875.html)

Then, pause SLA when issue is transitioned to Scheduled status.

* [Understanding why an SLA is paused in a Jira Service Management ticket](https://confluence.atlassian.com/jirakb/understanding-why-an-sla-is-paused-in-a-jira-service-management-ticket-1271267987.html)
* [Create service level agreements (SLAs) to manage goals](https://support.atlassian.com/jira-service-management-cloud/docs/create-service-level-agreements-slas/)


Tags: cloud

jira-service-management-cloud
Issue types
Asked by Drew Montagna:

Hello,

I recently added an issue type in admin\>project settings. However, when I try to add the issue type to my team based project, it doesn't appear. Additionally, many of the issues in the admin area don't appear, only Epic, Bug and Story.


Answers:
author: GNarsimhagowda - Empyra
body: Hi [@Drew Montagna](/t5/user/viewprofilepage/user-id/5426440) ,

There will be changes for team managed and company managed projects, the issuetype you have added to comapny managed project will not appear in team managed projects

For reference : [Difference between comapny managed and team managed](https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/)

comments: author: Drew Montagna
body: thanks.

How is a service desk portal created?


author: GNarsimhagowda - Empyra
body: Service portal would have been already created If you go to **project setting** s in that **portal settings** you will have the link to the customer portal.

Thanks.


author: Nic Brough -Adaptavist-
body: You create a JSM project - each one has a portal.


author: Drew Montagna
body: Okay. How do I access it?  
Is it located in the projects' settings?


author: GNarsimhagowda - Empyra
body: Goto Project settings\>Portal settings , You will have the URL to the portal

![2024-02-15_17h35_52.png](https://community.atlassian.com/t5/image/serverpage/image-id/306616iB3F8D02B079ECA7D/image-size/large?v=v2&px=999 "2024-02-15_17h35_52.png")


Tags: cloud

jira-service-management

jira-service-management-cloud