Dexter de Vera Community Champion

Actually you need to export the automation 1 by 1. Maybe you can do a workaround. Try to export 1 by 1 atleast 5-10 automations(choose a automation that had not been use for a long time). then delete that automations. Try to export again the global automations. then import the 5-10 automation (deleted before). 

File limit: Your JSON file must be 5MB or smaller. If your file is too big, you can export your rule in multiple segments.

Hi @Steve Morales , Welcome to the Atlassian Community! You can import csv to create issues in bulk. You may check the link how yo import csv in Jira cloud. https://support.atlassian.com/jira-software-cloud/docs/create-issues-using-the-csv-importer/ 

Hi @Lientur Hermosilla , Welcome to the Atlassian Community! I believe any PD custom field created with a formula derived field cannot be copied over by Jira automation.

Hi @Warren Wagstaff , Welcome to the Atlassian Community! You can checkout this trello templates: https://trello.com/templates/project-management/advanced-project-budgeting-and-time-tracking-2Hsb5dPy 

Welcome @Gilbert Figueroa ! 🥳🥳🥳

All Jira (JSM, JSW) automation Rule. https://support.atlassian.com/cloud-automation/docs/import-and-export-jira-automation-rules/

Hi @BX , Go to settings - System - Global Automation - (...) - Export rules

Hi @Mina Soultan , For each rule, select Edit and deselect the Enable checkbox at the bottom.

Adding approval in workflow * In your workflow - edit - Select Diagram if you’re not already in the diagram view. * Select the status you want to add an approval step to. * Check the box next to Include approval step. This option is only available if the workflow status has at least two transitions: one for Approve, and…

Hi @Ayush Pathak , SLA features is only available for Jira Service Management. This cannot be done in Jira Software unless you use plugin/addons.

Hi @Jhonatan Farias , * You can use the Epic as functionally/features/parts of the product that your planning to build/update. * Story for user stories expected by client. * Subtask for breakdown of task needs to be done per story. * Use version for quarterly major releases. * Some organise sprints around completing work…

Hi @Janice Jensen Yes. You can reset you cloud then do the migration again. You might want to take a look on this doc: https://confluence.atlassian.com/cloudkb/reset-and-delete-all-data-from-your-cloud-site-691012037.html Hope it helps!

No. That would be fine. No need to remove the license, you may just suspend the user so it will not count the license and can be activated anytime.

The view request in portal is only visible if request made f rom Jira portal or have request type. The 2nd screenshot is created directly in Jira. You can see the difference indicated in screenshot "raise this request via Portal" and the other one is "raise this request via Jira"

Hi @b_hafez , Base on your screenshot, the one was created via request portal and the one is in Jira. To make ticket visible in portal, you need to create the request via portal or select a request type in your jira ticket so it will align as request in portal.

@Chau Nguyen Minh , Welcome to the Atlassian community, It seems there is a current bug in linking issue in Jira software cloud. Maybe you can try it later again. Atlassian is now fixing this bug. https://jira-software.status.atlassian.com/ 

Hi @seunggabi , Welcome to the Atlassian community, It seems there is a current bug in linking issue in Jira software cloud. Maybe you can try it later again. Atlassian is now fixing this bug.

Hi @Sherwin Soriano , Welcome to the Atlassian community, It seems there is a current bug in linking issue in Jira software cloud. Maybe you can try it later again. Atlassian is now fixing this bug.

Add transition and screen per supplier operators.

Hi @Ray Balmeo Cagayon , Maybe you can try a workaround by making supplier field mandatory in creation of subtask. Then create 2 field for operation1 and operation2. Second add 2 transition and screen for both operations moving to done. Then create a workflow condition to hide the trandition base on supplier field value.…

Hi @Frankie Greenwood , Welcome to the atlassian community, If your company email useraccount are all company task related, you can just create new one with your personal email for personal purposes..

Hi @Ray Balmeo Cagayon , This cannot be done in automation. For workaround you may update your workflow and add stage/status for escalation level. So they can escalate to next level by transitioning the status.

https://www.linkedin.com/in/dexter-de-vera-5782b8139/

Hi @adam.clifford3 , Create a scheduled automation (run 1st day a Month) Then lookup: "Date of Birth" >= startOfMonth() and "Date of Birth" <= endOfMonth() Then send email and add email content: {{#lookupIssues}} <a>{{summary}} - {{Date of Birth.format("dd MMM")}}}</a> {{/}}

Happy to help.

Hi @Mathew Fidge , Welcome to the Atlassian community! Do you mean no site & org admin? You can raise a request in https://support.atlassian.com/contact/ about it. Hope it helps!

Happy to help! 

You may add this smartvalue to your email content- {{initiator.displayName}} ei. {{issue.key}} deleted by {{initiator.displayName}}

Hi @Matt Wangler , Have you tried to close your browser then retry it? If still had an error, you can raise a ticket in Atlassian Support .