youngmon/atlassian-qna huggingface dataset:
Concurrent Builds in Bamboo Specs
Asked by talleym:

Has anyone been able to use concurrent build in Bamboo Specs? I found the following issue when trying to migrate existing plans to specs:

1. Export plan using a max of 10 concurrent builds as Java Specs. Exported plan contains the following:

```
.pluginConfigurations(new ConcurrentBuilds()
                .useSystemWideDefault(false)
                .maximumNumberOfConcurrentBuilds(10),
        new AllOtherPluginsConfiguration()
```

2. Import that same plan, then navigate to the miscellaneous section of the plan configuration. Concurrent builds are not enabled.

3. View the plan's Java Specs again. This time the plugin configuration does not include concurrent builds:

```
.pluginConfigurations(new ConcurrentBuilds()
                .useSystemWideDefault(false),
        new AllOtherPluginsConfiguration()
```

I'm simply exporting and re-importing the same code. Is there some issue with the concurrent builds? Or am I missing some other configuration piece?


Answers:
author: Marcin Gardias
body: Hi, this problem has been fixed in the latest release (6.6.1)

comments: author: talleym
body: Hi! Thanks so much!


author: Jeremy Owen
body: Hey Megan,

Thank you for bringing this to our attention!

You're not missing any configuration, no. There's certainly a bug here and I was able to reproduce it only when overriding Artifact Handlers in the Spec. There's a chance other custom plugins that add settings to the miscellaneous tab could trigger it too (which I've yet to test).

Any chance you're also doing this with your Spec? Would you be able to share the *AllOtherPluginsConfiguration()* part of your spec? E.g. Anything within:

```
new AllOtherPluginsConfiguration()
 .configuration(...)
```

I haven't been able to find a workaround aside from removing the Artifact Handler override but I'll keep looking.

I've raised a bug report which you can follow below:

* [Concurrent Builds override can be lost when publishing Bamboo Specs](https://jira.atlassian.com/browse/BAM-19974)

Cheers,

Jeremy

comments: author: talleym
body: I see from Marcin's response that it's fixed in the latest release. Thank you for your help!


Tags: developer

spec
Atlassian Virtual Assistant - Edit Standard Flows
Asked by Ryan Johnson:

It would be helpful to have more customization available with the Virtual Agent's Standard Flows. According [to this article](https://support.atlassian.com/jira-service-management-cloud/docs/edit-a-standard-flow/) it only appears possible to remove the "Greet" flow.   

The messages as is are a bit noisy right now. It would be nice to edit the number for messages for things like "auto-close" to turn off the CSAT or remove the follow up CSAT message to provide additional feedback.   

Is there any option to do this or plan to implement?


Answers:
author: Birgit P
body: Same issue - we consider that as a barrier to rollout. We work with very fast-paced conversational ticketing and this would just create too much noise.


author: Joseph Chung Yin
body: [@Ryan Johnson](/t5/user/viewprofilepage/user-id/4645653) -

We have not utilize this functionality extensively yet. I would recommend you to contact Atlassian Support (<https://support.atlassian.com>) to obtain further assistance so the VA development team can participate in the ask.

Sorry.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.


Tags: cloud

jira-service-management

jira-service-management-cloud

virtual-agent
How to create an issue from an alert in JIRA cloud with Operations integration
Asked by Jason Ross:

I am working in JIRA Cloud and have a Service Management project. I want to have issues created in that project when alerts are fired from the Operations page. However, all the documentation that I can find discusses doing this with the non-integrated OpsGenie, whereas we are using the integrated version. For example, the documentation below mentions things that don't exist, like the integration option to create an issue from an alert. Is this even possible? Note that I am not asking to create incidents; I want an issue on our SM board to be created when conditions are appropriate as determined by the alert.  

Interestingly, I thought Sync would be a way to do this, but it does the exact opposite of what I want. It creates alerts for every issue, when I want an issue for every alert (or at least a subset that I can tune.)

[https://confluence.atlassian.com/jirakb/jsm-opsgenie-how-to-create-jira-issues-when-receiving-an-incoming-call-1252426041.html#:\~:text=OpsGenie%20site%20URL.-,Go%20to%20Teams%20%3E%20Integrations%20%3E%20Select%20Jira%20Service%20Management%20integration.,according%20to%20your%20use%20case](https://confluence.atlassian.com/jirakb/jsm-opsgenie-how-to-create-jira-issues-when-receiving-an-incoming-call-1252426041.html#:~:text=OpsGenie%20site%20URL.-,Go%20to%20Teams%20%3E%20Integrations%20%3E%20Select%20Jira%20Service%20Management%20integration.,according%20to%20your%20use%20case).


Answers:
author: Jason Ross
body: It appears that this cannot be done on the Standard plan that we have, since the OpsGenie functionality was rolled out to us and wasn't something we had purchased or owned in stand-alone form: <https://support.atlassian.com/opsgenie/docs/automatically-create-an-incident-via-incident-rules/>  

Great to know. We'll not be using this.


Tags: cloud

jira-service-management

jira-service-management-cloud

opsgenie
Is there a way to create and use/reuse Task Templates?
Asked by asadeh:

We are looking for a way to create and use (and reuse) templates for different reoccurring tasks. For example:

Let say we need to on-board a new client. That task might always have 7 different sub tasks, each might be assigned to someone else (or a different role). We would like to be able to create a template for this task that includes these sub tasks in it.

We would then like to be able to open a Service Management issue and either select an issue type that is associated with that template or load a template from a list of existing ones.

We believe we can use a custom filed "Task Type" with a project automation that will create sub tasks based on the value of that field. However, that is not an easy way to create or maintain this.

P.S. - it would be nice if the template can also have the option to define a specific starting status for each sub task, so that a each sub task can have its own applicable workflow.


Answers:
author: Trudy Claspill
body: Hello [@asadeh](/t5/user/viewprofilepage/user-id/3783993)

Are you willing to consider a third party app to satisfy your requirement? If so you might want to look at the options available in the Atlassian Marketplace. Here's a search to help you get started.

[https://marketplace.atlassian.com/search?hosting=cloud\&product=jira\&query=issue%20template](https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=issue%20template)

There are several apps that provide issue templating functionality.

As for the workflows being different for different subtasks, Workflows are applied to issues based on Issue Type. Are you going to make define multiple Issue Types at the Sub-task level? And will this be in a Company Managed or Team Managed project? Currently Team Managed projects don't support creating multiple Issue Types at the Subtask level.


Tags: cloud

jira-core

jira-service-management

jira-service-management-cloud

jira-software
How can I pull a customers asset information into an issue through automation?
Asked by tyler mikkelson:

I'm pretty new to JSM and still trying to figure everything out. However, I'm trying to create some automation that would allow me to see the Asset Object assigned to the Issue Reporter.

For example, if a customer submits an issue, then this automation would autofill an "Asset" field in the issue with the serial number of the Asset Object they have assigned to them.

I can't seem to figure out how I can connect the issue with the asset object like that.


Answers:
author: tyler mikkelson
body: This is what I've configured so far ![2024-04-02 13_44_47-Assets object_s field configuration - JIRA ? Mozilla Firefox.png](https://community.atlassian.com/t5/image/serverpage/image-id/315836i9AECFE3064EC98E8/image-size/large?v=v2&px=999 "2024-04-02 13_44_47-Assets object_s field configuration - JIRA ? Mozilla Firefox.png")

comments: author: tyler mikkelson
body: "Device Assignee" is an additional field I added to the "Laptop" Object Type


author: tyler mikkelson
body: Ended up resolving my own issue. Using objectTypeID = "ID" number rather than the written name resolved the issue


Tags: cloud

jira-service-management

jira-service-management-cloud
Create issue and link with existing issue
Asked by AI:

I am trying to create an issue via Jira REST API on Postman and Link that issue to existing issue in JSM based on custom field.

Is there any way to Link the issue with existing issues.

Here is my Json to Create an Issue in Jira.

"fields":{  
"project":{  
"key":"APPI"  
},  
"priority":{  
"name":"Low"  
},  
"summary":"Test_P2",  
"description":{  
"type":"doc",  
"version":1,  
"content":\[  
{  
"type":"paragraph",  
"content":\[  
{  
"type":"text",  
"text":"Description Test"  
}  
\]  
}  
\]  
},  
"issuetype":{  
"name":"Problem."  
},  
"assignee":{  
"name": "as"  
},  
"customfield_1000":"Request type",  
"customfield_1031":\[{'test':  
"customfield_1015":"Test_Hard",  
"customfield_1030":"Test",  
"customfield_1031":"Plants",  
"customfield_1032":"line"


Answers:
author: Kalyan Sattaluri
body: Hello,

Please review below link:

<https://confluence.atlassian.com/jirakb/how-to-use-rest-api-to-add-issue-links-in-jira-issues-939932271.html>

You can use solution 2 from above if you want to do it at the time of issue creation, or,

if you want to do it in 2 steps, do it like in solution 1, that is, create your issue, and then make a call to [POST rest/api/2/issueLink](https://docs.atlassian.com/software/jira/docs/api/REST/latest/#issueLink-linkIssues) ..

comments: author: Kalyan Sattaluri
body: Hello. The JSON you have shared isnt valid..

I was able to create an issue and link using below JSON. You can just pass a smart value for the issue you want to link it to and also change link type as needed..

```


{
"fields": {
"project": {
"key": "SUP"
},
"priority": {
"name": "High"
},
"summary": "Test_Postman1",
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "paragraph",
"content": [
{
"type": "text",
"text": "description"
}
]
}
]
},
"issuetype": {
"name": "Task"
}
},

"update": {
"issuelinks": [
{
"add": {
"type": {
"name": "Blocks",
"inward": "is blocked by",
"outward": "blocks"
},
"outwardIssue": {
"key": "SUP-1"
}
}
}
]
}
}
```


author: AI
body: I have updated the Json, getting below error

Error : {"errorMessages":\[\],"errors":{"priority":"Field 'priority' cannot be set. It is not on the appropriate screen, or unknown."}}

I have verified the Priority screen its already existed in Create Screen and edit screen  
{  
"fields":{  
"project":{  
"key":"NJP"  
},  
"priority":{  
"name":"High"  
},  
"summary":"Test_Postman1",  
"description":{  
"type":"doc",  
"version":1,  
"content":\[  
{  
"type":"paragraph",  
"content":\[  
{  
"type":"text",  
"text":"description"  
}  
\]  
}  
\]  
},  
"issuetype":{  
"name":"Problem"  
}  
},  
"update":{  
"issuelinks":\[  
{  
"add":{  
"type":{  
"name":"Problem",  
"inward":"Problem Link to",  
"outward":"Problem linked by"  
},  
"outwardIssue":{  
"key":"NJP-44"  
}  
}  
}  
\]  
}  
}


Tags: cloud

jira-service-management

jira-service-management-cloud
Move parent ticket (Epic) and child tickets together to a new project
Asked by Morgan Manns:

I am migrating one of our departments from a Team-Managed Jira Software project to a Company-Managed Service Management project. I've recreated everything to be as similar as possible in a way that makes sense and now I am working to migrate all open tickets over (about 200 open tickets and 3000 closed tickets). I have no problem migrating/moving tickets that don't have parent/child relationships, however I am struggling with Epics that have child ticket relationships. Does anyone have any tips on how I can move parent/child tickets together? Currently, I get a warning message saying:

**"Some issues will lose the relationship with their parent epic.**

You're moving some issues away from their parent epic. To avoid losing the relationship between these issues and their parent, move the epic issue as well.

Note: The epic relationship won't be lost when moving between classic projects."

Secondly, does anyone know any filters/queries I can use to move them together?


Answers:
author: JM Perrot
body: Hello [@Morgan Manns](/t5/user/viewprofilepage/user-id/5435505) thanks for your question,

One filter to get Epic and their children in you team managed project can be :

```
project = ABC AND (parent != EMPTY OR issuetype = Epic)
```

With this request, you'll get all the issues (including subtasks) with a parent and your epics.

If not, have you tried using automation to link issues? I don't know if it works, but you can make an automation rule in your team management project to link issues with their Epic. Once you've done this, you can "reverse" the rule to recreate the Epic-Issues relationship based on the link you've created. Don't forget to create a specific link beforehand.

comments: author: Morgan Manns
body: JM, thank you for sharing the filter!

I'm thinking this may be the easiest way to go about it to make sure everything gets moved over still intact. If anything else comes to mind, please let me know. I wasn't planning to move all closed/done epics and sub tasks as well, but if that's the only way to ensure they stay together, may be best. Appreciate the help!


author: Morgan Manns
body: JM, do you know of a filter that will get all *open* parent epics and also child issues only associated with the open parent epics pulled?


Tags: cloud

jira-service-management

jira-service-management-cloud
Linked Issue Update Automation
Asked by John Lord:

Hello,

I am stuck on an automation I want to set up thats a little complicated. I want to set an automation up that when fields on the linked issue are updated, it copies the updated fields to the linked issue (I think the correct term might be parent issue).

For example: Project A requests support from Project B for an issue to be on the next release. Project B reviews and updates the fix version field to show this will be included in the 4/2/2024 release. When Project B updates that field, the original issue from Project A has the fixed version field to match what Project B put in the field.


Answers:
author: Rebekka Heilmann _viadee_
body: Hi [@John Lord](/t5/user/viewprofilepage/user-id/5435545)

How are the two issues linked? Is it per "issue link" or are they in a parent/child relation (like Epic and Task or Task and Sub-Task)?

You would simply listen for changes in the field in Project B and then update any linked issues or parents/children in Project A. The problem is, that Versions are specific to a Project. You need a Version with exactly the same name in each Project before the **global** Automation Rule works.

You need to be Jira Admin to create global Automation rules that span 2 or more projects. The rule would look something like this:

![Screenshot 2024-04-02 170409.png](https://community.atlassian.com/t5/image/serverpage/image-id/315805iDC4EAA0B81269EE2/image-size/large?v=v2&px=999 "Screenshot 2024-04-02 170409.png")

Trigger: You watch changes in the Fix version field. You can restrict that to added values, specific Issue operations etc.

Condition: Check whether the change happened in Project B

Branch: Use "Branch rule / related Issues"  
This works for linked issues (restrict on the correct type of link you are using) and also for Parent/children issues.

Action: Edit Issue fields  
Make sure to Copy from Trigger Issue and un-tick the checkbox "add to existing values"  

![Screenshot 2024-04-02 170611.png](https://community.atlassian.com/t5/image/serverpage/image-id/315806i5798E903BD74459C/image-dimensions/265x226?v=v2 "Screenshot 2024-04-02 170611.png")


Tags: automation

cloud

jira-service-management

jira-service-management-cloud
Create report showing number of "request types" received
Asked by Drew D.:

Good day, all! I need to create a report that will provide the count of all requests received to our service project by "Request Type" Example 20 for password reset, 50 for Security, etc. I am uncertain about how to create this, any guidance would be appreciated!


Answers:
author: Trudy Claspill
body: Hello [@Drew D.](/t5/user/viewprofilepage/user-id/5467316)

Welcome to the Atlassian community.

Unfortunately Request Type is not yet available in the native statistic gadgets that can be used in a Jira Dashboard. There is a change request for there here:

<https://jira.atlassian.com/browse/JSDCLOUD-1914>

A work around is described here (link is in the above change request):

<https://confluence.atlassian.com/jirakb/how-to-use-request-type-field-or-affected-services-field-in-jira-gadget-reporting-1369277804.html>

You might also find third party apps that add more dashboard gadgets that would enable you to create a statistical report based on Request Type. At least one such app was mentioned in this post:

<https://community.atlassian.com/t5/Jira-Service-Management/Is-it-possible-to-create-Pie-Chart-according-to-Request-Type-in/qaq-p/1087263>


author: Hannes Obweger - JXL for Jira
body: Hi [@Drew D.](/t5/user/viewprofilepage/user-id/5467316),

if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2658949).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields - including all JSM fields - much like you'd do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) *issue hierarchies* , *issue grouping* by any issue field(s), *sum-ups* , or *conditional formatting*.

With these, you can build a request type report like e.g. this one in just a couple of clicks:

![request-type-report.gif](https://community.atlassian.com/t5/image/serverpage/image-id/316070iD4FC56B09E564DA3/image-size/large?v=v2&px=999 "request-type-report.gif")

Note that this is really just one of a virtually endless number of possible reports - you can also view and group by any other issue field(s).

Could this help with your use case?

Any questions just let me know,

Best,

Hannes


Tags: cloud

jira-service-management

jira-service-management-cloud
Automation rule execution limit for single project automation rules in data center ?
Asked by Mina Soultan:

Please specify the automation rule execution limit for **single project automation rule (not global rule )** for Jira service management data center


Answers:
author: YY Brother
body: Hi [@Mina Soultan](/t5/user/viewprofilepage/user-id/5439581)

Welcome to our Community.

As far as I know, there's no automation execution limit for JSW DC.

Thanks,

YY?


Tags: data-center

jira-service-management

jira-service-management-data-center
Can't download Attachment from mail
Asked by Mathis CHAUMETTE:

Hello,

<br />

On some of our issues, we have a form below the issue, that we fill in like this :

![form2.PNG](/t5/image/serverpage/image-id/315763i8793D32FF245A1B5/image-dimensions/367x468?v=v2 "form2.PNG")

Once you've filled in the form and clicked send, an automation is activated, the form is automatically converted into a PDF attachment, and an email is sent with a link to download the PDF.  

![form4.PNG](/t5/image/serverpage/image-id/315768i6AA0FE2B81FB3AEE/image-size/large?v=v2&px=999 "form4.PNG")

For agents, they can download the attachment with the link of the mail, but for internal customers (without a licence), they have this error in the browser :

![form3.PNG](/t5/image/serverpage/image-id/315766i27733B73B5FF2230/image-size/large?v=v2&px=999 "form3.PNG")

Is there a solution to this problem?


Answers:
author: Kris Dewachter
body: Hi [@Mathis CHAUMETTE](/t5/user/viewprofilepage/user-id/5467241) ,

Welcome to the Community.

Can you check the following:

* Does the customer have access to the portal?
* Does the customer have access to the ticket in the portal?
* What are the attachment access settings ? See <https://support.atlassian.com/jira-service-management-cloud/docs/set-up-how-your-customers-access-attachments/>

Best regards,

Kris

comments: author: Mathis CHAUMETTE
body: Hi Kris,

Yes, the customer have access to the portal and he have acces to the ticket in the portal.  

For the attachment access settings, we have select "Download the attachments via a secure link (without logging in)

Thanks for your answer,

Mathis


author: Kris Dewachter
body: Hi [@Mathis CHAUMETTE](/t5/user/viewprofilepage/user-id/5467241) ,

Upon closer inspection, I see in your screenshot the form is marked as "Internal". Can you also check if the attached PDF is also marked as internal ?

If so, it's correct that customer are not able to access it.

Best regards,

Kris


author: Mathis CHAUMETTE
body: Hi [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367) ,

I switch the configuration, now the form is "External", but even with that, the customers have the same error.  

For information, I followed this procedure : <https://confluence.atlassian.com/jirakb/jira-automation-403-forbidden-when-opening-email-attachments-sent-to-customers-1206791694.html>

Thanks,

Mathis


author: Mathis CHAUMETTE
body: It's resolved, in the automation, you must remember to make the comment visible to the public to give the rights to download the file!

Mathis


Tags: cloud

jira-service-management

jira-service-management-cloud
Jira SD unassigned queue is empty, not showing team coffee run -message
Asked by Van Dijk:

Ok, minor thing. But I noticed that after migrating from Server to Cloud, the empty (unassigned tickets) queue is showing this:![Screenshot 2024-04-02 161733.png](https://community.atlassian.com/t5/image/serverpage/image-id/315777i7EDA5EE4771C2E8B/image-size/large?v=v2&px=999 "Screenshot 2024-04-02 161733.png")

<br />

It use to show the "team coffee run" message or similar which was more fun.  
How to get that showing? Or can it be customized to something funnier?


Answers:
author: Rebekka Heilmann _viadee_
body: Hi [@Van Dijk](/t5/user/viewprofilepage/user-id/3235720)

You cannot "customize" the message that's displayed while a queue is empty.

Is that your question?

comments: author: Van Dijk
body: That was my other question yes :) I found the jira suggestion for that:  
<https://jira.atlassian.com/browse/JSDCLOUD-4386>  

But when our queue is empty we do not see those default messages (mentioned in the ticket above) but that pic I added instead. So wondering where I could set it up to show even those default messages:  

*Currently if a queue is empty, the message will either display*

* *Your queue is empty. Team coffee run!*
* *Your queue is empty. High five your neighbour!*
* *Your queue is empty. Cupcakes for all!*


Tags: jira-service-desk-cloud

jira-service-management

jira-service-management-cloud
Why is my scan folder empty? (using Insight Discovery)
Asked by Steve M?lon:

Hello there,   

We have successfully set up and configured Insight Discovery and we have configured the initial import in an empty schema.

I would like now be able to run multiple imports on different schemas. The problem is: the scan folders is always empty.

Is the file being "consummed" once imported?

Many thanks!


Answers:
author: Harla Batinovic
body: The Cloud import function actually deletes the file once it has been transferred to JSM.


author: Fabrizio Tatti
body: Same issue here


Tags: cloud

jira-service-management

jira-service-management-cloud