david_fsrxhm Atlassian Partner

Hi @Jenny Amari check the Notification Schemes as probably you or a group that you belong, are included in some events triggered by the issues. You can find more info about the Notification Schemes here: https://confluence.atlassian.com/adminjiracloud/creating-a-notification-scheme-776636401.html PS. You need to be a Jira…

Then will be deleted also from Jira, there are some exceptions depending on the configuration between your Jira and AD but usually will be deleted too, that's why is better to disable them from the AD instead of deleting.

Hi @Madhu Reddy the best approach is to use Automation Lite so you can create rules for created issues and apply them the needed config (like permissions schema or issue types). You need to select the Customer Request Type that you have config in Service Desk configuration: And then capture this request type in Automation…

Hi @Trang Vo yes, you need to have both. They may seem the same but they are not because the permission scheme applies to all the project and the workflow only to some Issue Types. They can be the same or not. Cheers, David

Hi @Patrick Sacher The good practice is not deleting the users like you said, there is a lot of data to preserve. When you have Active Directory what you can do is to disable the person there (not delete it) and when sync with Jira will be disabled there too.

I wish I knew about Atlassian's roadmap :) so far they said in the last Summit that they will make the NextGen Projects grow, is a priority for them

Hi @David Rodriguez not subtasks as we know them. What you can do it create easily another issue types in Project Configuration. What you can do is linking issues, even though they have different types Cheers, David

Hi @Catherine Sullivan did the solution work?

You welcome :)

Hi @Jehosúa Ibuarben unfortunately this is stone-written Atlassian policy and yes, you have to pay for the app for whole users you have in the instance. Cheers, David

I'm trying to find the way I got this id and it seems I could do it in previous Jira versions from the Issue Navigator. I typed the Request Type and the ID appeared, I pasted in Automator and that's all. (Try this and see if you can see the Id in the advanced search). But now that we updated to Jira 7.8 always shows the…

Hi @Fernando Jimenez, unfortunately is not possible to use many features that we have with classic projects like Categories or quick filters. Atlassian said that they will be adding those in the future. In addition you can use an app like Profields that allows you to have Project Fields. Cheers, David

Hi @Manuel Adalid I had your very same issue weeks ago when configurating Automator and filtering by Request Type. I solved using the id instead of the name: "Customer Request Type" = "suppsd/0cbe0ffb-9c34-4aac-a758-0e82e98e6dd2" I hope this helps Cheers, David

Hi @Priyendu Bhardwaj every standard issue type can have subtasks by default, always that they are included in the Issue Type scheme. Cheers, David

Hi @Fernando Jimenez, unfortunately is not possible to use many features that we have with classic projects like Categories or quick filters. Atlassian said that they will be adding those in the future. Cheers, David

Hi @Andre Wiggins there's no need to recreate the project as you will loose every issue and configuration. Just create another workflow with issue types and try until they feel confortable. The issues will remain and just the config will change. Cheers, David

Hi @Mauricio Payetta it seems to be a bug, users should be able to change their language in their profile without a problem. If they change another preference, does it work? Cheers, David

Also is possible that haven't created a team yet, at the moment that you create it, you will be Team Admin and will be possible to invite users

Sure, this is what I meant, you should be inside the Team selecting it in the Home screen

Hi @Catherine Sullivan be sure that you are inside the Team site:

Sorry Lovi, I sent the wrong link, this one covers what you need https://confluence.atlassian.com/adminjiraserver/migrating-from-jira-cloud-to-server-applications-938846963.html Cheers

As the integration is set in Bitbucket as an app, the configuration there only accepts one Jira instance. We are talking about Cloud, aren't we?

I would recommend to separate them into different Issue Types so you can filter easily by them in case that they behave differently. You can also use custom fields that will apply to issues and allow you to set specific information for them.

Is difficult to say a number because it depends on the resources of your Jira machine but we can say that when your instance begins to run slow, to take so much time to index or upgrading is becoming difficult because of the number of apps, then is time to review them. Also depends on the grade of support that vendors…

Hi @Allister check the Email Queue screen under Admin menu in Jira Cheers, David

Hi @Abhijith Jayakumar the next-gen projects are standalone board based. They are designed to be like that

Happy to hear that is solved Martin and thanks for sharing the original problem. Btw, I have colleagues that assure that writing an email to support@atlassian.com opens a ticket but I haven't checked myself. Cheers, David

@Madhu Reddy don't worry, deactivated users don't count for the license limit

Hi @Madhu Reddy the best practice is not deleting users but to disable them. This will prevent you from having problems. Is that an option? Cheers, David

Hi Lovi, answering your questions: * Even though is not mandatory is recommended, the more common project format to Data Center, the better. * Not in theory, just the inner info from next gen projects like roadmap details. * Better to read this article from Atlassian that explains a…