Hey all!
I recently ran a "Jira DC→Jira Cloud" session over on the free public classes lately and wanted to share our Q&A.
Below is the Q&A - but please flag your questions about DC→Cloud changes, and be sure to check out the FREE public classes over in Atlassian learning.
Question 1 - Where do you ID the project under "create"?
- In the Jira Cloud "Quick Create" modal, the space selector appears at the top left of the modal alongside the issue/work type selector. Clicking the name allows you to switch between spaces.
Question 2 - Is grouping on boards new?
- Grouping options across list, board, and timeline views in Jira Cloud have evolved significantly compared to legacy Data Center views, allowing dynamic groupings by assignee, epic, status, or subtask.
- Board admins can also use the "query" option to create custom ones with Jayquill ("JQL")
Question 3 - When you do search do you still get JQL prompting?
- Yes. In Jira Cloud search, you can enter natural language queries or switch directly to the JQL editor. Additionally, Atlassian Rovo can generate and translate plain-text requests directly into valid JQL statements.
- Jayquill still works from Filter → Search Work Items
Question 4 - Is Rovo native with cloud or does it need to be turned on and configured? What are the barriers in orgs of implementing Rovo?
- Rovo is natively built into Atlassian Cloud paid instances and is typically enabled by default, but organization administrators have the ability to toggle it on or off at the org level.
- Major adoption barriers include internal compliance policies, data privacy concerns (e.g., GDPR), and security assessments regarding AI access to company data.
- Every group will make their own determination on whether or not to use Rovo, and to what extent.
Question 5 - Managing automations and keeping track of them in a large environment for admins. Now that they are native, how is that tracked?
- Automations (now called Automation Flows) are tracked either at the space level (Space Settings > Automation) or globally across the instance (Jira Settings > System/Automation). Admins manage them using descriptive naming conventions (such as prefixing with the Space Key), categorization labels, execution audit logs, and performance error checks.
Question 6 - How do I create quick board filters?
- To create a quick filter on a board in Jira Cloud, you must be a board administrator. Navigate to Board Settings > Quick Filters, provide a name, and input the desired JQL query (e.g.,
priority in (Highest, High)). The filter will then display as a clickable toggle button at the top of the board.
Question 7 - Is there anything you suggest we should do before a migration actually happens?
- Avoid a blind "lift and shift". Use the migration as an opportunity to clean up technical debt: audit custom fields, archive inactive projects/spaces, consolidate duplicate workflows, review compliance requirements with legal, and start user change-management and training early.
- Ensure everyone gets training! This includes admins, end users and everyone in between (pro tip - LOADS of free stuff on Atlassian Learning!).
Question 8 - How much time should we allow for users to get used to the change in feature in Cloud?
- Typically, allow 1 to 4 weeks for users to achieve baseline comfort with the interface shift. Hands-on User Acceptance Testing (UAT), pre-migration demo videos, and clear change communications significantly reduce downtime and user friction.
- Typically I keep reminding/training/informing until folks tell me "we got it, stop!".
Question 9 - For users is it a case of learning on the go? What training do you recommend? Can you provide any links?
- While informal "learning on the go" happens, relying on it alone causes frustration. Structured self-paced modules and free live classes provide a much smoother transition. Key free resources include the Transition to Jira Cloud track on Atlassian Learning and the free community learning catalog.
