Hernan Halabi Community Champion

Two comments, I recall Jira is case sensitive for groups, might be the case for users as well. Make sure you type the whole username. If your user doesn't have browse users permissions it won't be suggested unless you type the whole username on that box. After you find the user you will be able to change the role which…

Hello @Gyanendra Kumar welcome to the community. Assuming that the deferred stories have such status (deferred) you can update your agile board filter not to bring issues in that status

Hello @Girish_Kulkarni link below it's a bit old but functionalities are still the same https://www.atlassian.com/blog/confluence/link-jira-issues-to-confluence-pages-automatically

I'm not seeing any attachments, could you please add them again?

Hello @Christian Körner maybe the post function isn't working for checkbox fields. Rather than troubleshoot a lot. I would try to clear the field with the Automation module

Hello @Jean-Michel BARTHEZ welcome to the community. If you are using the server version that would be called users and roles.

Hello @Benson_So keep in mind that the collaborators are users that have browse project permissions and would certainly need to have permissions to add comments as well. Make sure that the permission scheme grants those permissions to the roles you are using. With that in place I would expect the users to be able to see…

Hello @Dominik Appel I don't think you will be able to figure that out from Jira. What I have seen in the past is that at the email server level the different aliases emails are moved to different folders and then you build incoming mails services to fetch the data from each folder into Jira as a separate thing but I'm not…

Hello, it's very odd that is failing based on what you share. Was it the same config in cloud? Have you run an integrity check to make sure there are no errors there?

Yes, ideally you install both solutions in the same Jira application. I would do that and do project imports to merge both instances instead of taking the trouble to add apps that allow you to sync the projects between them. 

Hello @Yeisol Woo welcome to the community. Make sure that the users have a service desk license as well as project admin along service desk agent permissions on the project.

Hello @Suporte AGTI have you checked the mandatory fields for the request type? There you can make fields mandatory that they are not from the agents view 

in cloud? the new interface will be the only interface pretty soon so I would suggest start using it anyway.

Hola @Dulce_Gabriela_Hernández_Esquivel bienvenida a la comunidad. La versión corta sería de que los correos deben ser respuestas del primer mail o bien deben tener el número del ticket como parte del asunto del mail. Puedes tener más detalles revisando está documentación…

Hello @Janine_Memon a query like this should work sprint in openSprints ()

I don't recall if those are shared by default but based on the information I have. That would be a no.open the ticket and see if the organization field has a value. 

That's per project only and you can't do the same with internal notifications that would be the ones used by Jira software

Hello @Arthur Harutyunyan take a look to eazybi app. You can create the same reports and make use of eazybi dashboard that allows you to have global variables, in this case the dates. So you can change the date at the dashboard level and all your reports will be updated based on that criteria

Hello @Tanya Morgan when you create the ticket are you sharing it with the organization? If you don't, then the organization field ends empty and therefore the queue will fail. 

Hello @Michael Smith that can be done with SLAs and the module Automation if you have service desk. If you don't it would imply automation for Jira app and some queries. What are you currently using?

Hello @Angel I believe this is what you are looking for https://support.atlassian.com/jira-service-desk-cloud/docs/change-the-look-and-feel-of-customer-notifications/

Why not just have a queue for these types of requests? Agents might even see it sooner than their email since in theory they are supposed to be working within Jira to manage their tasks?

So you have a Jira instance for software and a different one for service desk instead all in the same server? I would have expected to have all in the same Jira installation. If this is the case the solution will be completely different

That should be working. Can you send some screenshots of the project settings? Also the query results. If you can see both projects you should be able to query for both of them

Hello @Julio Banegas why not use the latest automation addition? It's should be pretty straightforward there. Nevertheless I would suggest you have a special queue for those requests. An agent should be focused on the queues rather than checking their emails to see if something new has happened in Jira 

Hello @Vitor Lima I suggest you check apps like tempo timesheets that are time tracking oriented

Hello @Milo Grika I'm not sure how to do it directly with automation but I'm thinking that this might work as well. Setup an sla that works with a calendar with just work days. Then at automation after a new ticket is created, check if that sla is running. If it is, send the email.

Yes.. all that is part of the built-in functionalities from Jira will migrate. Add-on specific config will need to be replicated manually

Hello @wdonovan welcome to the community. The configuration from the workflows won't work even though you are going to have the same addon in cloud. You will have to recreate all that configuration when you migrate. Optionally, consider working ahead and replicate the workflow on a test cloud environment and then export…

Then you just need to and save the filters (first link). It could be a filter as simple as Project in (jsdkey, softwarekey) and resolution is empty Just add the project keys there and you should get all tickets that haven't been resolved yet on both projects