youngmon/atlassian-qna huggingface dataset:
Yaml specs version 1 -> version2
Asked by Aske Jenstrup Olsson:

Hi,

How is it possible yo upgrade the yaml specs for a project in Bamboo.

I've upgraded the yaml specs, but I get the following error message when the specs are parsed:

```
Bamboo YAML import failed: Plan with name: 'PD-Build' already exists in project 'PD'. Can't create a new one with same name.Do you need help? Please visit the http://docs.atlassian.com/bamboo/docs-0609/Bamboo+Specs+troubleshooting page.
```

I would like to keep the build history of the old plan

Regards,

Aske


Answers:
author: Alexey Chystoprudov
body: It should be

```
---
version: 2
plan:
  project-key: PD
  name: PD Build
  key: BUILD
```

comments: author: Aske Jenstrup Olsson
body: Yeah - I messed up in the version 1 yaml spec with two keys, used the wrong one...

Thanks


author: Lenin Raj
body: Hi [@Aske Jenstrup Olsson](/t5/user/viewprofilepage/user-id/2387972)

Are you importing a new "plan" via v2 instead of updating the existing v1 spec?

comments: author: Aske Jenstrup Olsson
body: I was just updating the bamboo.yaml specs to version 2:

from:

```
project:
  key: PD
  plan:
    key: PD-BUILD
    name: PD Build
    key: BUILD

stages:
  - jobs:
      - scripts:
          - '#!/bin/bash'
          - './gradlew clean build'
        testParsers:
          - type: junit
            testResults: '**/build/test-results/**/*.xml'
```

to:

```
---
version: 2
plan:
  project-key: PD
  name: PD Build
  key: PD-BUILD

stages:
  - Build:
      jobs:
        - Build

Build:
  tasks:
    - script: |
        #!/bin/bash
        if [ -f bamboo-specs/ci_build.sh ]; then
          chmod +x bamboo-specs/ci_build.sh
          ./bamboo-specs/ci_build.sh || exit 1
        else
          ./gradlew clean build
        fi
    - test-parser:
        type: junit
        test-results: '**/build/test-results/**/*.xml'  
```


author: Aske Jenstrup Olsson
body: Hm, while replying I see there are 2 keys in plan section of the original yaml spec. Maybe that is the issue.

-Aske
Microsoft teams integration with Jira
Asked by sdudekula:

Jira integration with Teams works on the web version but not on the desktop version. It fails to approve permissions when Jira is added as an app to Teams.


Answers:
author: Pallavi Shirodkar
body: Hi [@sdudekula](/t5/user/viewprofilepage/user-id/5522599)

Once you add the app to teams, it usually takes maximum 5-6 Hours to work on the Desktop version. Also once you add the app to teams you can try re-starting your teams and check once.

Even i was facing the same issue, it got resolved.

Thank you!


author: Nicolas Grossi
body: [@sdudekula](/t5/user/viewprofilepage/user-id/5522599) Welcome, could you please post the error you are getting ?

Nicolas


Tags: cloud

jira-service-management

jira-service-management-cloud
Emails sent to the default email account are not creating JIRA tickets
Asked by Paul Terry:

An email was sent to the default email account of one of our projects over 5 hours ago and it still has not created a JIRA ticket.

Is there an ATLASSIAN issue?


Answers:
author: Nicolas Grossi
body: [@Paul Terry](/t5/user/viewprofilepage/user-id/4757524) You might contact support.atlassian.com as your account is standard.

Nicolas

comments: author: Paul Terry
body: Done, thank you


Tags: cloud

email

jira-service-management

jira-service-management-cloud
Reminder email using Jira Automation rules
Asked by Ken Camarador:

Hi All,  

I am trying to figure out a JQL to achieve my goal, but unfortunately, my query is not working as expected.

**Goal:** Set up an automation rule to remind approvers about pending ticket approvals. The rule should run every day at 7 AM, find tickets that have been pending approval for more than 2 days, and send a reminder email. If the status remains unchanged, another email should be sent every 2 days.

**What I have done so far:**

1. Created a scheduled cron job to run every day at 7 AM with the following JQL:

**approvals = pending()**

2. Created an IF: ANY condition to match tickets with the following criteria:

* **`created = -2d`**
* **`created = -4d`**
* **`created = -6d`**

However, no queries are showing up. If I use `created <= -2d`, it shows me tickets that are 2 days old or less, causing it to send emails every day.

How can I modify my JQL to only find tickets that have been pending for exactly 2, 4, and 6 days?


Answers:
author: Walter Buggenhout
body: Hi [@Ken Camarador](/t5/user/viewprofilepage/user-id/5522540) and welcome to the Community!

You could consider a couple of things, a first being more restrictive in your query. If you want to only select issues created more than 2 days ago, but less than 4, the following might work:

```
created <= -2 days AND created >= -3 days
```

You can then use similar criteria to deal with 4, 6, ... days. But if you have to deal with very unresponsive approvers, you may find yourself creating lots and lots of conditions in your automation rule.

So, to be a bit more dynamic, you could - after 2 days - send a first reminder and use a custom date field to also add the current date to your issue *(e.g. reminder date).*Once you've done that, you can then use the reminder date instead of created to make sure you send a new reminder mail, thus reusing the same logic for as long as it takes to get your issues approved.

Hope this helps!


Tags: cloud

jira-service-management

jira-service-management-cloud
Send an email to the component lead
Asked by Luc Grangier:

We'd like to send an email to the component lead when we close a ticket related to that component. I tried several scenarios (Automation, Transition, Notifications schemes), but none of them worked. We'd like to avoid installing an additional add-on on our cloud instance. Is there a solution?


Answers:
author: Fernando Eug?nio da Silva
body: [@Luc Grangier](/t5/user/viewprofilepage/user-id/3994194)

As Nicolas mentioned, there is no built-in way to do this.

One way you can try is to combine automation with Jira's REST API within automation.

In short, the component structure does not display the lead component and if you did a direct GET on /rest/api/3/component/{id}, you would only have the accountID of the lead component. You would need a third action using a GET User by account ID: /rest/api/3/user

To then find out the email of the component lead.

It might be a little harsh, I imagine. But it is one of the few ways without the support of an add-on that will be able to retrieve your component lead's email.


author: Nicolas Grossi
body: [@Luc Grangier](/t5/user/viewprofilepage/user-id/3994194) I think that this feature is not possible as built in currently. You might want to open a suggestion on jira.atlassian.com.

HTH

Nicolas


Tags: cloud

jira-service-management

jira-service-management-cloud
How should we announce the availability of customer portal to our internal users? [Onboarding Users]
Asked by Alexander Hammond:

We are onboarding Jira Service Desk for our internal users to submit IT help tickets and tickets for other work. Our users currently aren't aware of this, is there good documentation or templates Atlassian has provided to onboard our users successfully?   

I'm not looking for technical onboarding, I'm looking for awareness onboarding, and things to highlight for our users as they learn of and begin using this new tool for requesting support and help.


Answers:
author: Dan Breyen
body: Hi Alexander, as every implementation is different, I don't think there's a standard onboarding process.

I've been sending my customers something like this in an email:

Hi \<employee\>, we are reviewing your \<issue desc\> issue. \<My Company\> is implementing a new Support Portal to better assist you with any questions or issues you may have. You can also sign up for an account via the portal link here: https://\<siteURL\>/servicedesk/customer/portals

Thank you,  

You could easily send something like that to all of your staff. You could also create a little how to demo video for them if you wanted.

I also created a few Knowledge Base articles with screenshots with what they can expect and how to enter a ticket, you can include them in the email too.

Hope that helps

comments: author: Alexander Hammond
body: Thanks Dan! I like that its short and sweet, a video I could record is a good idea too.


Tags: cloud

jira-service-management

jira-service-management-cloud
New request form fields automatically appear in other requests issue views
Asked by Leon Gumba:

I'm having an issue in Jira Service Management where adding fields to a new request type affects all my existing request types.  

For example, I have 10 different request types like Complaint, Dispute, Compliance, CRM, etc. I recently created a new request type called Legal and added around 15 new fields to its request form. However, these 15 fields now appear in the issue view of all my other request types (Complaint, Dispute, etc.), not in their request forms, but in their issue views.  

This has caused a big mess, and now I have to manually remove these fields from each issue view of the other request types. Is there a way to add fields to a new request type without affecting the existing ones? How can I manage this better?


Answers:
author: Florian Bonniec
body: Hi [@Leon Gumba](/t5/user/viewprofilepage/user-id/5487256)

If all request type shared the same issue type, if you add fields to a screen for 1 request type, it will add for all of them because they are sharing the same issue type so same screen scheme. You could create a new issue type with new screen just for legal, and map this request type to the new issue type.

Regards

comments: author: Leon Gumba
body: [@Florian Bonniec](/t5/user/viewprofilepage/user-id/495589) thank you for your input!  

Yes, it turned out that all of the request types were tied to the same issue type, which is why the new fields appeared in all the old request types.  

I have now created new issue types and associated them with the respective request types, plus I created new screens for those.  

Awesome, thank you so much for your help!


Tags: cloud

jira-service-management

jira-service-management-cloud
IVR Integration
Asked by Brady Buttrey:

I am looking to integrate an IVR solution with my Jira Service Management Data Center Help Desk. Does anyone know how this would be done and/or if there are any IVR solutions that integrate best with JSM?


Answers:
author: Ash Yadav
body: Hi [@Brady Buttrey](/t5/user/viewprofilepage/user-id/5459170)

This question has been asked previously and I believe the answer is still valid today:

[https://marketplace.atlassian.com/apps/1217009/chat-sms-voice-and-video-for-jira-service-management?hosting=cloud\&tab=overview](https://marketplace.atlassian.com/apps/1217009/chat-sms-voice-and-video-for-jira-service-management?hosting=cloud&tab=overview)

As of right now, there doesn't appear to be any options natively available within JSM.

It might be best to reach out to IVR providers directly to see if they have any suggestions for integration.

KR,

Ash

comments: author: Brady Buttrey
body: Is there no way to integrate it using Rest or potentially by creating an automatic email of an unconnected IVR voicemail transcript to be sent to JSM email?


author: Ash Yadav
body: This would likely be part of some custom development that a team would undertake in-house. I suppose you won't know until you try.

There is a DC supported add-on here that I've found: [https://marketplace.atlassian.com/apps/1223383/cisco-finesse-integration-for-jira?hosting=datacenter\&tab=overview](https://marketplace.atlassian.com/apps/1223383/cisco-finesse-integration-for-jira?hosting=datacenter&tab=overview)

I'm not associated with the developer in any way, just thought it might help. The rest of the add-ons appear to be exclusively for Cloud (support for Avaya for example).

KR,

Ash


Tags: jira-service-desk-data-center

jira-service-management

jira-service-management-data-center

jira-service-management-server

server
Limit in the displayed (dropdown) values
Asked by Oksana Vyzhutovich:

Did any limit appear in the displayed (dropdown) values of the field?

We have a field which contains approximately 70 dropdown values and now when scrolling the list of values we can see only 50 values. Two days ago we could see all 70 values.


Answers:
author: Vijay Dadi
body: Please verify at what transition the field is behaving like this. Open the properties for that particular transition, there might be a possibility that someone excluded some of the values which can be done as below

jira.field.\<field\>.exclude 10000,20000

hope this helps !

comments: author: Oksana Vyzhutovich
body: thank you for suggestion. The field behaves like this without transition. Perhaps it was just a bug, since from today all drop-down values ??are displayed


Tags: cloud

jira-service-management

jira-service-management-cloud
welcome mail not received by specific user
Asked by BKT Helpdesk:

welcome mail not received by specific user (dineshchandra.singh@bkt-tires.com). Kindly let us know what is the issue?


Answers:
author: BKT Helpdesk
body: correct mail id dineshchandra.singh@bkt-carbon.com


Tags: cloud

jira-service-management

jira-service-management-cloud
Major Incident Indicator is missing
Asked by Vijay Dadi:

Hello,

When I mark an Incident as Major Incident, the label on top of the issue is missing.

This works for opsgenie incidents but not for incidents created via portal or with JSM.

Quick help is appreciated.

TIA

Vijay


Answers:
author: Cedric Devaux
body: Hi Vijay,

I have the same issue when ticket is created from the portal the indicator does not appear.

I create a ticket to Atlassian, I wait an answer.

On your side do you find a solution?

Cedric


Tags: cloud

incident

incident-management

jira

jira-cloud

jira-service-management

jira-service-management-cloud

major
Ticket owner from email header
Asked by Andriej Michajlowski:

Hi

I new to JSM and have a requirement which I wasn't able to fulfil. My current workflow with JSM is as follows:

1. User submits an online support form (Wordpress + Contact Form 7)

2. An email is generated and sent to support@domain to notify support team of a new request. This email has a Reply-To: header which contains the email address of the user submitted the online form.

3. JSM is configured to access the support@domain using IMAPS protocol.

4. A new ticket is created in JSM

5. The ticket is reviewed and assigned to a specialist based on the ticket content.

6. Ticket addressed and Closed

The issue that I have is that I can't figure out how to configure JSM to use the Reply-To header to assign the ticket owner to. As the form contents are emailed from the service email account, JSM recognises all tickets to come from the same ticket owner/creator. I would like the ticket owner/creator to be based on the Reply-To header and not on the From header. How / where Do I configure this? Is there a better / easier way to do a ticket generation from the Contact Form 7?

Thanks for your help

Andriej


Answers:
author: Andriej Michajlowski
body: Any thoughts, suggestions, recommendations on this?


Tags: cloud

jira-service-management

jira-service-management-cloud

wordpress
Move JSM Subscription for Email Origin Domain
Asked by Rajat Samseriya:

We are an engineering partner for another company and manage their Jira project (development) under our domain (Hinditron). We provide similar services for other clients as well. However, for one customer's support (Jira Service Management), we need the support emails to originate from their domain email address (xyz@customer.com).

**Request:**

Could you advise whether we should move the JSM subscription directly under their account to achieve this, or if it is better to maintain it under ours? We seek guidance on the best approach to ensure the emails are sent from the desired domain.


Answers:
author: Nadhila Savira
body: Hi Rajat,

Nadhila here from Atlassian.

I see you had submitted the same question here: <https://community.atlassian.com/t5/Jira-Service-Management/Should-We-Move-the-JSM-Subscription-to-the-Customer-s-Account-or/qaq-p/2728257>

Could we compile our discussion in one post to avoid confusion please? Thank you!


Tags: cloud

jira-service-management

jira-service-management-cloud
Standard Filters
Asked by Marieke van Zaal:

Hi,

When I select my project and then choose 'view all issues', I see a number of filters in the left toolbar under the heading 'standard filters'. Where can I adjust these default filters?

Thank you very much!

Kind regards,

Marieke


Answers:
author: Duc Thang TRAN
body: Hello [@Marieke van Zaal](/t5/user/viewprofilepage/user-id/5516947)

Here a document to let you know how to edit a queue: [https://support.atlassian.com/jira-service-management-cloud/docs/create-a-new-queue/](https://support.atlassian.com/jira-service-management-cloud/docs/edit-queues/)

comments: author: Marieke van Zaal
body: Hi Duc,

Thank you for your response. I want to edit the Default filters (see print screen below). These are different from queue's right?

Thank you so much!

Kind regards,

Marieke![Scherm?afbeelding 2024-06-17 om 12.28.01.png](https://community.atlassian.com/t5/image/serverpage/image-id/330140iCB3959FC2123DC68/image-size/large?v=v2&px=999 "Scherm?afbeelding 2024-06-17 om 12.28.01.png")


author: Duc Thang TRAN
body: Hello [@Marieke van Zaal](/t5/user/viewprofilepage/user-id/5516947)

Your screen is for filter .

If you're looking for a solution to edit the default filter in Jira, I'm afraid that's not currently possible. You can find more questions about this topic in community, and here is a suggestion that's currently under consideration.

<https://jira.atlassian.com/browse/JRACLOUD-63317>


author: Marieke van Zaal
body: Thank you. This is what I was looking for. So it cannot be done at this moment. Although people have been asking for this feature for years.

Do you perhaps know, why our issues that are marked 'done' still show up in the 'open issues' filter?

thanks again!


author: Nadhila Savira
body: Hi Marieke,

Nadhila here from JSM.

Our default filters recognise tickets with the Resolution field filled in as truly closed tickets. If nothing had been added to the Resolution, then our system sees the ticket as still open.


author: Marieke van Zaal
body: Hi Nahila,

Thanks for your response. We do have Resolutions like the one called 'Done' (see printscreen).

In our workflow we have Linked our status 'Gesloten' (=done) tot the category 'Done'.

What am I missing here? Thank you so much for your help!

![Scherm?afbeelding 2024-06-18 om 14.40.00.png](https://community.atlassian.com/t5/image/serverpage/image-id/330379i9AE9996AE6EF6401/image-size/large?v=v2&px=999 "Scherm?afbeelding 2024-06-18 om 14.40.00.png")

![Scherm?afbeelding 2024-06-18 om 14.34.38.png](https://community.atlassian.com/t5/image/serverpage/image-id/330377iADC4D80AA7337CA8/image-size/large?v=v2&px=999 "Scherm?afbeelding 2024-06-18 om 14.34.38.png")


author: Marieke van Zaal
body: Since we are not able to edit System Filters, can anyone explain to me why issues that are marked 'done' still show up in the 'open issues' filter?


Tags: cloud

jira-service-management

jira-service-management-cloud
[JQL] Join different fields
Asked by ???_??_:

Project A (Jira Software)  
Project B (Jira Service Management)  

A Project issue type: a, b, c  
B Project Field options: a, b, c  

<br />

Although they are different fields, I want to filter issues as if they were one field.

Please tell me JQL.


Answers:
author: Ste Wright
body: Hi [@???_??_](/t5/user/viewprofilepage/user-id/4704901)

Can I clarify the logic here?

* You want to query issues in Projects A/B
* Search for different field values based in Project A/B

...is this correct?

---

Is this an either/or scenario? For example:

* Find all issues in Project A which are Stories or Bugs, OR
* Find all issues in Project B where Priority is High or Medium?

JQL might then be...

```
project = "Project A" AND issuetype in (Story, Bug) OR project = "Project B" and priority in (High, Medium)
```

---

If this is not what you need, let us know more specifics so we can help further :)

Ste

comments: author: ???_??_
body: Hi, [@Ste Wright](/t5/user/viewprofilepage/user-id/1166470)

Thank you for your interest.

Issue types for Project A: apple, banana, orange  
Project B's Custom Field options: apple, banana, orange

Filter all issues in Project A and analyze issue types.  
The issue type of Project B is different from Project A.  
So Project B used custom fields to distinguish fruits.

Current: I wrote separate charts for A and B.

Conclusion: I want to extract A and B at once and check which fruits were produced in the most in one chart.


Tags: cloud

jira-service-management

jira-service-management-cloud
r?activer un membre
Asked by Eicnam AAS:

Bonjour, j'aimerais r?activer un membre de l'?quipe \<email removed\>

Merci


Answers:
author: Ste Wright
body: Hi [@Eicnam AAS](/t5/user/viewprofilepage/user-id/5522228)

Welcome to the Community!

Just to let you know, I've removed the user's email address. This is a public forum, and it's best not to post personal information on here.

In terms of your request - are you a Site Admin looking for assistance? Or requesting reactivation from your Administrators?

If you are an Admin, you should be able to reactivate a user's access here:

1. Go to <https://admin.atlassian.com/>
2. Select your Organization (if needed)
3. On the top navigation bar, select *Directory*
4. Locate the user in the list. You might need to change the "Filters" to show all users
5. Reactivate the user and/or provide them access to products again

You can find more on this help page: <https://support.atlassian.com/user-management/docs/deactivate-a-managed-account/>

If you aren't an Admin though - you just need to contact your IT Support Team, or the team who managed your Atlassian instance, and ask them to reactivate the user :)

---

And in French (according to Google Translate)...

Bienvenue dans la communaut? !

Juste pour vous informer, j'ai supprim? l'adresse e-mail de l'utilisateur. Il s'agit d'un forum public et il est pr?f?rable de ne pas y publier d'informations personnelles.

En ce qui concerne votre demande, ?tes-vous un administrateur de site ? la recherche d'aide ? Ou demandez-vous une r?activation aupr?s de vos administrateurs ?

Si vous ?tes un administrateur, vous devriez pouvoir r?activer l'acc?s d'un utilisateur ici :

1. Acc?dez ? <https://admin.atlassian.com/>
2. S?lectionnez votre organisation (si n?cessaire)
3. Dans la barre de navigation sup?rieure, s?lectionnez R?pertoire
4. Localisez l'utilisateur dans la liste. Vous devrez peut-?tre modifier les \<\< Filtres \>\> pour afficher tous les utilisateurs
5. R?activer l'utilisateur et/ou lui redonner acc?s aux produits

Vous trouverez plus d'informations sur cette page d'aide : <https://support.atlassian.com/user-management/docs/deactivate-a-managed-account/>

Si vous n'?tes pas administrateur, il vous suffit de contacter votre ?quipe d'assistance informatique ou l'?quipe qui a g?r? votre instance Atlassian et de leur demander de r?activer l'utilisateur :)


Tags: cloud

jira-service-management

jira-service-management-cloud