Marc -Devoteam- Community Champion

Hi @Deepika.Kanaparthi You can reach Atlassian Support via this link: Atlassian Support 

Hi @Kurtis You need an to have an incoming transition to the status "Waiting for Approval". I see only outgoing transitions from that status, so you would need to modify your workflow. So if you move the issue to the project, to a status in the shown workflow, there needs to be a transition outgoing from that status to the…

Hi @Theo JEAN JEAN This is strange. The only thing that might be the issue is, are you using Team Managed or Company Managed projects. This function only works in Company managed projects. See documentation here

Hi @Deepika.Kanaparthi I suggest to reach out to Atlassian Support in relation to such a migration. You will run into time outs related to the amount of data you want to import. See if they can assist in this migration.

Hi @Anupama Kota Welcome to the community. See the following article on how to remove your site.

Hi @Christian Joel You and I already have the new Improved user management experience See bottom part of the article. Old Cloud instances use the top section of this page. This way on managing accounts is slowly faced out and everyone will move to the new experience..

Hi @Theo JEAN JEAN This works on my instance. I can't reproduce your results if issues are children of epic in the same project. If I run the exact same query related to issues in my instance, I see all Epic and children.

Hi @Joe W_ If you want to have a uniform setup in relation to action on multiple projects the Company Managed projects are the way to go. Team managed projects are containers, no configuration set in these projects or automation rules setup to multiple projects can be used. I can't tell you, that it worked fine before.…

Hi @Joe W_ I suspect that you have Team managed and Company managed projects in your instance. Make sure all your projects are company managed if you want to make use of shared configuration items.

HI @Theo JEAN JEAN You could use the function parentEpic. This will filter the Epic and all it's child issues. You can specify mutliple epics in the query Example: parentEpic in (dkp-10) parentEpic in (dkp-10,dkp-11,dkp-17)

HI @Lucas Tavares Welcome to the community. Apps are related to a Jira instance not to individual projects in Jira.

Hi @Rene Jonathans Welcome to the community. This is not Atlassian Support, but a community of Atlassian enthusiasts, that are willing to help other Atlassian users in relation to issues they face. Any bug or feature related to the product is a question to raise at Atlassian Support.

Hi @BenWade Not this can't be done. Your requirement is a filter, create this filter and set a subscription to yourself on the filter to notify you on the issues with missing information. Roadmaps are also only a visual overlay of Jira issues, it's for planing purposes. So all the system available warnings are related to…

Hi @Kurtis The automation to set the issue to another state should be able to work. What is the configuration of your rule and what is the error that is given on running the rule. Are there conditions or validators on the workflow that prevent the status change?

Hi @[deleted] The none option can be removed by making it mandatory on a request or setting it as required in the field configuration scheme. The last will have impact on all issue typers related to the field configuration scheme.

Hi @flim Custom Field context, is a best practice to any custom field.

Hi @Christian Joel See products section and you should be able to manage each of your products

Hi @Klime Buneski What is the config of the Assets CF looks like. I think it might that the option multiple is not enabled in the Asset CF field.

Hi @Eric Hansen Asset Discovery relies on agents installed on server to gather the content and create patterns for scanning and who to set the date into assest to be used within Jira Service Managment. See documentation here on how to use the discovery agent

Hi @Joe W_ The issue lies with the field Customer. Is that field still available on the project? So look at: * Custom Field context * Is the custom field ID still correct? * Field Configuration * Field Configuration Scheme

HI @Evert Morren / @Evert Morren Atlas Admin What is the Filter used in the Crate series? See the example from @Asha Goyal Remove the type option in this case to remove the request type option.

Hi @Danielle David These users require at least the Developer role on the schema level.

HI @Evert Morren Atlas Admin What is the configuration of your report? What series are you using on the report. It's most likely the JQL related to one of the series provides the Request Type information

Hi @flim You can try the following workaround. * Create a "Request Group" Custom Field of type "Select List (single choice)". Create a "New Context" specific to this project, where you will manually include in the list all "group" options that already exist in your project. * Include this custom field in all request types…

Hi @pzotos No you can't these services are related to Opsgenie integration with JSM. There is also no report option based on dependencies in Opsgenie

Hi @Joe W_ Welcome to the community. Can you provide more details on your automation rules (screenshots). - Full rule details - errors the rule is giving Is domain a custom field? Does the field with ID still exist< and is it on your screen, has it been removed from a field configuration, has the context of the CF field…

Hi @Jakeer Welcome to the community. No you can't this would require an app like scriptrunner, exalate or issue synchroniser Or you could look on how it might be possible to trigger an automation rule with a webhook that creates a cloned issues in the other instance. I think there are some community topics on this.

Hi @pzotos Welcome to the community. Unfortunate not. As you don't have depended fields relations with in Jira.

Hi @Rodney Mort It all depends how your structure within the company is. You could have 1 project for all work that's team related or can't de handled by your service engineers in the agreed SLA, or it's a change that needs to be planned. Issues can be linked via issue linking, I do suggest you to use Company Managed…

Hi @Christian Joel You need to have the org admin permission to make the changes mentioned on the article you mention in your request.