youngmon/atlassian-qna huggingface dataset:
Will the OpsGenie Mobile app keep working after migration to Jira Service Management
Asked by Lothar:

Hi,

Atlassian has scheduled to pull the plug on OpsGenie as from October 2024.

We now have the option to migrate our OpsGenie Teams, schedules and integrations manually or wait for atlassian to do it automatically in October 2024.

Nowhere in the" Start moving"- or "Set up operations"-documentation I find any reference on what will be the impact on the mobile Opsgenie app.

Will it keep working as before? Will we be needed to reinstall, re-register our account or reconfigure? Or will we be forced to install a different app altogether?

This is an important piece of information for all organizations that use OpsGenie for 24/7-support as we do. We will need to be able to switch within business hours of 1 business day in order to respect our SLA's.

I'm sure we are not the only client with this concern, so has anyone heard anything officially about this?

Kind regards


Answers:
author: Kevin Patterson
body: Hi [@Lothar](/t5/user/viewprofilepage/user-id/5170452)

Atlassian recently launched a new streamlined ops experience, see here: <https://community.atlassian.com/t5/Jira-Service-Management-articles/An-update-to-incident-management-in-Jira-Service-Management-and/ba-p/1962985> . If your JSM environment is using this new experience the old OG mobile app will no longer work. You will need to have your responders download the Jira mobile app (they've recently added alerts and on-call details in the app). <https://www.atlassian.com/software/jira/service-management/mobile-app>

If you are an existing JSM customer that does not have the new streamlined Ops experience the existing OG mobile app will still work.

I was not aware Atlassian was pulling the plug on Opsgenie this October, can you reply with a link that references this?

comments: author: Kate Clavet
body: Hi [@Lothar](/t5/user/viewprofilepage/user-id/5170452) and thanks [@Kevin Patterson](/t5/user/viewprofilepage/user-id/5497084) for your answer!   

The timeline that you see is the timeline given to merge to the new experience. It does not mean that Opsgenie standalone will be shut off at that date, it just means that your individual instance will be read only at that point because you have moved to the new experience.   

Customers can request more time if needed, on a case-by-case basis. Here's a post that explains a bit more about that: <https://community.atlassian.com/t5/Jira-Service-Management-articles/It-s-time-to-streamline-your-operations-in-Jira-Service/ba-p/2733798>  

We are also holding an AMA on August 8 if you'd like to join and ask any additional questions you may have. The AMA link is in the article I shared above.   

Thanks,   
Kate


Tags: cloud

jira-service-management

jira-service-management-cloud
How do I modify the EazyBI reporting?
Asked by Ghosh_ Arghanil:

How do I modify the EazyBI reporting?  
Would like to edit and modify to make a custom report for managing asset's details.


Answers:
author: Gerda Granti?a
body: Hi [@Ghosh_ Arghanil](/t5/user/viewprofilepage/user-id/5532936)   
For creating and managing eazyBI reports, you need to have at least a "User" role for the particular eazyBI account, see more here: <https://docs.eazybi.com/eazybi/set-up-and-administer/manage-accounts/account-users>

best,  
Gerda // support@eazybi.com


author: Lisa Forstberg
body: Hi [@Ghosh_ Arghanil](/t5/user/viewprofilepage/user-id/5532936)

Welcome to the community!

If having the right permission you can make own reports, copy existing reports and amend them. EazyBI is enormously flexible. I recommend using all the good resources available on their site: <https://docs.eazybi.com/eazybi?eazybi-for-jira>

best of luck

Lisa


author: Alexey
body: First - duplicate the report. After this you can modify it with User Interface or programmatically with calculated measures.


Tags: cloud

jira-service-management

jira-service-management-cloud

jira-software
Automation: How to identify the receiving inbox in email requests?
Asked by Paul Heath Armengol:

We have two inboxes for the same project and requests should be assigned to a different person depending on the receiving inbox.

How can we identify the receiving inbox in an automation?


Answers:
author: Lisa Forstberg
body: Hi [@Paul Heath Armengol](/t5/user/viewprofilepage/user-id/5040545)

The JQL fields available is a bit limited in this area. you can use request-channel-type = email to see if it came in via email but not to which email address.

A workaround is perhaps to assign different request types to each address? Use that to differentiate between them to be able to build automations on top of that.

regards

/L

comments: author: Paul Heath Armengol
body: Thanks Lisa.


Tags: automation

cloud

jira-service-management

jira-service-management-cloud
Hi, Time to SLA add on can be used for both service management and jira software tickets
Asked by busra_baybars_partner_yildizholding_com_tr:

Hi,

Currently we are using jira service management for our IT services, but we are going to migrate cloud to data center. And Data Center we are going to use Jira software (Jira) for each team and we will set un integration with sm and sw projects. Each team can manage the ticket for their software projects. In that situation we are going to use time to SLA add-on to calculate SLA's of software tickets, but in the same time we have to calculate the SLA's of the tickets in the service management site. So how we can configure one SLA calculation for both software and service management tickets?


Answers:
author: Lisa Forstberg
body: Hi [@busra_baybars_partner_yildizholding_com_tr](/t5/user/viewprofilepage/user-id/5447972)

The standard SLA fields are limited to Jira Service Management but as you mention you are going to use the Time to SLA addon for the purpose of having an SLA on the Software ticket. This means that you need to ensure that these two SLA's are configured exactly the same at all times.

I think this might work but I think you can reduce complexity through keeping your operations tickets in the Jira SM project and instead use a Team label /Team field / Asset object field when you assign it to a team instead and build boards that contain the operations tickes for each team?

br

Lisa


Tags: cloud

data-center

jira-service-management

jira-service-management-cloud

jira-software
Bug - When in a filter view we click on a ticket, sometimes randomly it opens the wrong ticket.
Asked by Maximilien Borgeat:

When in a filter view we click on a ticket, sometimes randomly it opens the wrong ticket.

I only noticed the bug at the filter view level.

This happens to all employees in my organization.

Technically when we click on a ticket to view it, it takes us to another ticket. If we go back to the previous web page opened in the tab, we come across the correct ticket. As if when you click on the ticket to open, it opens it and instantly opens another one.

Has anyone else encountered this problem? And if so is there an existing resolution? Or a ticket already opened with Atlassian regarding this bug.

Thank you for your feedback.


Answers:
author: Lisa Forstberg
body: Hi [@Maximilien Borgeat](/t5/user/viewprofilepage/user-id/4645073)

Ouch! I haven't seen this behaviour and I can't really reproduce it on my cloud sites now when I try. I would have screen recorded it and sent it in as [Bug report](https://support.atlassian.com/contact/) to Atlassian.

best of luck

/L

comments: author: David M?ller
body: Same happening for some users of my organisation since the last update... Would be great if you can share the solution if you!


author: Lisa Forstberg
body: Hi,

Well not all updates are rolled out to all sites at the same time so maybe a new update has not hit my sites yet. I recommend you to report this to Atlassian asap.

br

Lisa


Tags: cloud

jira-service-management

jira-service-management-cloud
Issues with Data Collection Using Jira Discovery Tool
Asked by Steffanie Schneider:

Hi Atlassian Community,

I have recently started using the Discovery tool in Jira for network and device scanning. However, I am encountering some issues and would appreciate some guidance.

When I scan from one device, I only receive data for that particular device. Is this the expected behavior of the Discovery tool? My understanding was that it should collect data from all devices on the network.

Do I need to install the Discovery tool on every individual device and perform scans from each one to gather comprehensive data? Or is there a configuration setting I might be missing that allows a single scan to capture data from multiple devices on the network?

Any insights or recommendations on how to correctly set up and use the Discovery tool would be greatly appreciated.

Thanks in advance!

Best regards,  
Steffy  


Answers:
author: Volodymyr Batrukh
body: Hi [@Steffanie Schneider](/t5/user/viewprofilepage/user-id/5479912)   

You need to install Assets Discovery tool only on one device having an access to the network you want to scan. Then you need to configure scan settings(set of nodes you want to scan) and credentials(with proper access method - WMI, SNMP, SSH). After you run scan from on Discovery tool it will collect data for all configured devices.   
Please find more information here - <https://confluence.atlassian.com/assetapps/configure-scan-settings-1168848068.html> and here <https://confluence.atlassian.com/assetapps/configure-credential-settings-1168847945.html>  

Regards,  
Volodymyr B.

comments: author: Steffanie Schneider
body: Hi Volodymyr B.,

Thank you for the detailed instructions on installing and configuring the Assets Discovery tool. I appreciate the clarity and the links provided for further information. This will be very helpful as I set up the tool.

Best regards,  
Steffanie Schneider


Tags: asset-management

assets

assets-discovery

cloud

discovery

discovery-tool

jira-service-management

jira-service-management-cloud
How can I find the actual parameters for API for example "protocol", "Host"?
Asked by Francis Luigie Tadeo Acuar:

How can I find the actual parameters for API for example what should I input in "protocol", "Host" via JSON.

this is the file name: user-management.postman


Answers:
author: Samuel Wilson
body: Hello,   

To find the actual parameters for an API, such as what to input for "protocol" and "Host" in a JSON file, you can follow these steps:

Open the Postman Collection: Import the user-management.postman file into Postman. This will give you access to the predefined requests and their configurations.  
Inspect the Requests: Look at the details of each request in the collection. Postman will show you the URL, headers, body, and other parameters used in the requests.  
Check the Environment Variables: Sometimes, parameters like "protocol" and "Host" are defined as environment variables in Postman. Check the environment settings to see if these variables are set there.  
Review the API Documentation: If available, the API documentation will provide detailed information about the required parameters, including "protocol" and "Host". This documentation is often accessible through the API provider's website.  
Example JSON Configuration:  

<br />

    {  "protocol": "https",  "Host": "api.example.com",  "path": "/user-management",  "method": "POST",  "headers": {    "Content-Type": "application/json",    "Authorization": "Bearer your_token_here"  },  "body": {    "username": "exampleUser",    "password": "examplePassword"  }}

<br />

Use Postman Console: The Postman console can help you debug and see the actual parameters being sent with each request. Open the console and make a request to see the details.  
By following these steps, you should be able to identify the correct parameters for your API requests.

<br />

`Best Regards,`  
`samuel898`  
[gm-socrates](https://www.gm-socrates.com)


Tags: cloud

jira-service-management

jira-service-management-cloud

not-applicable

organization-administration
Automation on last comment
Asked by Giorgos Savva:

Hi team,

I activated the following automation:

1. If comment \~ This can be closed

2. Then transition to DONE

What I need is to change the 'comment' to 'last comment'. The reason is that if the ticket reopens at a later stage, then the automation reads the comment again and closes it again.

Thank you in advance.


Answers:
author: Ravi Sagar _Sparxsys_
body: Hi [@Giorgos Savva](/t5/user/viewprofilepage/user-id/4065237)

You can access the last comment using {{issue.comments.last}}

Ravi

comments: author: Giorgos Savva
body: Thanks Ravi! It works also. Maybe it is a bit safer this way!


author: David Friedrich
body: Thanks for the infos. I created this rule with jira cloud automations and it worked. Reopened issue will not close on any other comment:

![2020-12-09 10_22_23-Clipboard.png](https://community.atlassian.com/t5/image/serverpage/image-id/121441i8BA88607F8CB14D6/image-size/large?v=v2&px=999 "2020-12-09 10_22_23-Clipboard.png")![2020-12-09 10_23_18-Window.png](https://community.atlassian.com/t5/image/serverpage/image-id/121444i9E7AD15891A75313/image-size/large?v=v2&px=999 "2020-12-09 10_23_18-Window.png")

comments: author: Giorgos Savva
body: Thank you David! It works :)


author: David Friedrich
body: Hi Giorgos,

happy to help, but i'd need more intel here ;-).  

Are you using Server/Data Center or Cloud?

Is your question about the integrated service desk automations or project automations provided by automation for jira app?

Thanks!

comments: author: Giorgos Savva
body: Hi David. I am sing Jira Cloud and project automations.
Automation for Jira - Server Plugin Closing out Parent task when creating Sub-task
Asked by lukec:

Pretty much what the title says. I have automation set up so that when a field value changes, a sub task for the issue in which the field was changed is created, and an email sent.

Both things happen as advertised, however the Parent issue for which the sub-task was created gets its Resolution put into Done. The Status is still In Progress, just the Resolution changes.

I don't see how to prevent this. Anyone else seen this? Have any ideas how to avoid it?

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


Answers:
author: lukec
body: Darryl you were right, had nothing to do with the automation. Nic had an answer in a different post... it was screen related. My mistake..

<https://community.atlassian.com/t5/Jira-questions/Updating-custom-field-sets-resolution-to-Fixed/qaq-p/259241>

comments: author: Darryl Lee
body: Interesting! Yeah, based on what you shared about Scriptrunner, I was going to ask if the behavior still manifest if you disabled the Automation.

Glad you found the fix. There's a reason Nic is a top-answerer!


author: Bill Sheboy
body: Hi [@lukec](/t5/user/viewprofilepage/user-id/3801781)

Have you checked your workflow to see if something else is setting the resolution?

What does the individual issue's log indicate about who/how the Resolution was set?

Best regards,

Bill

comments: author: lukec
body: Thanks [@William Sheboy](/t5/user/viewprofilepage/user-id/788946) ,

The only transition that modifies the resolution is when it goes to the Done status, as a post function.

But using the automation for jira plugin, if the issue stays in To Do status, or In Progress status.. and does not transition thru the workflow, the resolution is still changed when that field value is modified (thereby kicking off the automation).

The log shows that I marked it as Done, as seen below:

Luke C made changes - 09/Dec/20 4:39 PM

<br />

Field Original Value New Value  
Product categorization Parent values: Security(13076)Level 1 values: Incidents(13162)  
Resolution Done \[ 8 \]


author: Darryl Lee
body: Hrm, that log entry makes it look like Automation isn't involved at all. (If it was Automation editing the field, I think it would show up in a separate entry.)

Could it be a ScriptRunner Listener?


author: lukec
body: Thanks [@Darryl Lee](/t5/user/viewprofilepage/user-id/1365322)

I looked at the ScriptRunner Listener (I only have one set up) it just looks for SSNs, this test issue I made doesn't have anything resembling a 9 digit number. Here's the log from the plugin:

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

So ticket 257 is the parent.. 258 is the sub task that was created, and shows up on the parent ticket. But 257's resolution gets marked as Done when it shouldn't. Again it doesn't even move through the workflow at this point. All I'm doing to activate this automation is change a field value.


Tags: server
Jira Automation to remove fix version from child issue IF removed from parent Epic
Asked by John Carson:

Note that my epics are in a different project from the child stories. I have the exact same named version created in both projects. I have successfully created an automation that adds the fix version to the child story if a fix version is added to the parent epic.

New requirement: if I remove a fix version from the parent Epic I want to remove that exact same fix version from the child issue. There may be other fix versions on the parent and child that need to remain untouched, this needs to only work if the scenario is that the exact same fix version (by name at least) is set on the child as is removed from the parent Epic.

Any help is greatly appreciated.


Answers:
author: Bill Sheboy
body: Hi [@John Carson](/t5/user/viewprofilepage/user-id/835960)

Fix Version is a list field, and unfortunately there is no single item remove function for lists in automation yet.

I was able to make a work-around for this by converting a list to a string, removing the target item, and then converting back to a list. My example is for the Component field. Please take a look here if you want to try it:

<https://community.atlassian.com/t5/Jira-Software-questions/how-to-delete-specific-issue-components-using-automation-for/qaq-p/1534864>

Best regards,

Bill

comments: author: John Carson
body: [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)thank you very much for your attention to this. I will play with your proposed workaround today!
Automation for Jira - sending emails with URL
Asked by Giorgi Tsitsvidze:

Hi Atlassian community,

is it possible - using app automation for jira - to send email with issues button URL -

transition URL - when user in email click this URL issue moved on another status ...

best regards

Giorgi Tsitsvidze


Answers:
author: Bill Sheboy
body: Hi [@Giorgi Tsitsvidze](/t5/user/viewprofilepage/user-id/3926599)

For your first question, yes you can add a link to issues in emails using Automation for Jira. Try adding this in the email:

\<a href="{{url}}"\>{{key}} - {{summary}}\</a\>

With out of the box Jira you cannot do the second thing, adding a link to transition an issue to a different status. Perhaps providing the link to the issue will be enough as a person could open the issue and then transition it from the issue view page.

Best regards,

Bill


author: Daniel Ebers
body: Please note:  
this was also posted [here](https://community.atlassian.com/t5/Jira-Software-questions/Automation-for-Jira-sending-emails-with/qaq-p/1548107).  
You might want to check this link also for some more contributions that were made meanwhile.

Regards,  
Daniel


Tags: jira

jira-server

server
Create an automation rule to move issues to done when merge PR to a master branch (github)
Asked by Hender Ruiz:

we trying to create an automation rule when a PR is merged, but we want to transition the issues to DONE only when the PR were merge to the Master branch


Answers:
author: Tom Williams
body: [@Hender Ruiz](/t5/user/viewprofilepage/user-id/3927530)

This should work if the branch is called "Master".

![Screenshot 2020-12-04 094451.png](https://community.atlassian.com/t5/image/serverpage/image-id/120823iF1DFAB2D58A3EADA/image-size/large?v=v2&px=999 "Screenshot 2020-12-04 094451.png")

comments: author: Tom Williams
body: \^ You may also want to include a check that there are no other Pull requests open. You can do this using a JQL condition.

key = {{issue.key}} AND development\[pullrequests\].open = 0


author: Hender Ruiz
body: Thanks, I'm going to test this solution and let you know!


author: Mikael Sandberg
body: Instead of using an automation rule, why not use a workflow trigger instead? This is what workflow triggers are intended for, to transition issues when something happens in your development tool. Have a look at [Configure workflow triggers](https://support.atlassian.com/jira-cloud-administration/docs/configure-workflow-triggers/) for more information.
Update custom User Picker field
Asked by Paul Krueger:

I'm creating a rule that checks to see if a custom User Picker field is empty. If so, I want to populate it with the assignee of the issue.

Unlike the behavior for Assignee, the default options for the User Picker are:

![Screenshot 2020-12-02 120650.png](https://community.atlassian.com/t5/image/serverpage/image-id/120416iD24398C8A6CF714C/image-size/large?v=v2&px=999 "Screenshot 2020-12-02 120650.png")

None of those will reference the assignee value. How can I reference the assignee (or the assignee email address) so that I can populate this custom user picker field?


Answers:
author: Darryl Lee
body: You ***can*** populate a User Picker field with the Assignee value. You just need to choose from the (confusingly named) "Copy from..." operation in the little \[...\] button:

![copyfrom.png](https://community.atlassian.com/t5/image/serverpage/image-id/120594iE6D5CD79B14A9F4C/image-dimensions/392x218?v=v2 "copyfrom.png")

(I'm on Cloud - not sure if it's different on Server.)

comments: author: Paul Krueger
body: This totally worked and, once you actually get there, it makes sense. Thanks!


author: Bill Sheboy
body: Hi [@Paul Krueger](/t5/user/viewprofilepage/user-id/565954)

Have you tried the advanced JSON edit option yet? Please see here for information about that approach:

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

Best regards,  
Bill

comments: author: Paul Krueger
body: Thanks for the link. It was exactly what I needed. It took a bit of fiddling but this worked:

{  
"fields": {  
"customfield_10171": { "id": "{{assignee.accountId}}" }  
}  
}
Send email via automation for Jira fails
Asked by Clark Everson:

trying to send emails to a specific project role when a certain field is updated. When I try to send it to just the project role, it fails and says it's due to the value in the "to" field missing

![Screen Shot 2020-12-01 at 9.43.02 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/120204i250A55FC445F400B/image-size/large?v=v2&px=999 "Screen Shot 2020-12-01 at 9.43.02 AM.png")![Screen Shot 2020-12-01 at 9.49.11 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/120203i76D23A1241C26B2D/image-size/large?v=v2&px=999 "Screen Shot 2020-12-01 at 9.49.11 AM.png")


Answers:
author: Bill Sheboy
body: Hi [@Clark Everson](/t5/user/viewprofilepage/user-id/2969809)

I do not believe you can do that yet as there is an item in the Code Barrel backlog to add it:

<https://codebarrel.atlassian.net/browse/AUT-537>

As a work-around you could add a custom field (user list) for your developer people, populate the field on issue creation, and use that field as the "To" for sending emails.

Best regards,

Bill

comments: author: wwalser
body: I've linked this community question to that ticket in the hope that we can follow-up here should the ticket get picked up.


author: Boris Berenberg - Atlas Authority
body: Hi Clark,  

We support this in [Notification Assistant for Jira](https://marketplace.atlassian.com/apps/1211069/notification-assistant-for-jira-email?hosting=server&tab=overview) if you're on Server or Data Center. We're working to add this to our Cloud version as well.