🚀 Volume 7: Elevate your admin skills by enabling your teams to work faster

[#1]

Hey, Jira Admins!

We're back with fresh tips and helpful content for you and your users, and this time, we're focusing on the power duo of Jira and Rovo. If you haven't started sharing some of these tips and resources with your teams yet, consider starting this new practice for the year! If you’re looking for more, we also have an archive of past volumes for you to explore here!

🏆 And for those of you who might be up for a fun challenge during the month of March, check out our Jira Custom Onboarding contest, running now through March 26th! 

	💡 Empower your users As a Jira Admin, you play a key role in helping your teams manage projects, track progress, and complete tasks. We're here to support you! Choose a tip to share weekly over the next month with your organization’s Jira users via Slack, Teams, your company wiki, or email.
	Tip #1: Use Rovo to turn vague ideas into clear Jira issues ⭐️ Help your users go from “I think there’s a problem…” to a well-formed ticket in one pass. Instructions to share with users: When you’re about to create an issue but aren’t sure how to describe it: Open your team’s Jira project and click Create. In the description field, paste whatever you have: Slack snippets Error messages Meeting notes Rough bullet points Use Rovo (AI assistant) to: Summarize the problem clearly. Propose acceptance criteria (“done looks like…”). Suggest a priority based on impact and urgency. Before you hit Create: Adjust anything Rovo wrote so it matches your team’s language. Add any missing context about customers, environments, or deadlines. This turns messy raw input into a clear, actionable issue that’s easier for your team to pick up and complete.
	Tip #2: Turn long Jira comments and meetings into quick-read summaries with Rovo ⭐️ Help users keep up with work without rereading huge threads. Instructions to share with users: When an issue has a long activity stream or you’ve just had a working session: Ask Rovo directly on the issue: “Summarize the latest updates on this ticket.” “What decisions were made and what are the next steps?” Use the summary to: Get a quick “catch-up” if you were not in the meeting. Double-check that the owner, due dates, and next actions are clear. After review: Add or edit the issue description or a top comment using Rovo’s summary so: New collaborators don’t have to scroll through every comment. Stakeholders can get the gist in under a minute. This turns Jira into a source of concise status, not a wall of text.
	Tip #3: Use Rovo to find similar work before you reinvent the wheel ⭐️ Instead of rebuilding the same solution, teach users to ask Rovo what already exists. Instructions to share with users: Before you: Design a new workflow Create a new request type Log a “new” bug or improvement Ask Rovo something like: “Show me past issues similar to this one.” “Are there existing epics or projects that solved this problem?” “Is there a runbook or Confluence page for this kind of issue?” If you find something useful: Link the existing issue, epic, or doc to your current ticket. Reuse or adapt the pattern instead of starting from scratch. This helps teams reuse proven solutions, shrink duplicated work, and keep Jira cleaner over time.
	In this Demo Den episode, one of our engineers walks through a new Rovo AI feature that helps you quickly connect related work. Bring duplicate work together, centralize context, and get a complete picture of what your team is working on.
	Courses for your Jira users: Feb 26: JQL Functions - Finding Things in Jira 202 Feb 26: Jira Plans Deep Dive: Capacity Planning and Cross-Team Alignment Admin-focused learning experiences: Mar. 4: Teams & Organization Hierarchy in Jira Mar. 11: Goals & Projects in the native Jira Goals App!
	Community Champion @Nikola Perisic shows how to use Jira Automation plus a simple custom “Sub-task order” field to ensure work happens in a specific sequence—so the next sub-task can’t start until the previous one is truly done. If your teams struggle with parallel work starting too early or missing dependencies, share this walkthrough to help them set up clear, enforced handoffs.

[Savannah Ehrhardt]

Does 2 work for you? It doesn't work in my instance at least.

I can’t see any direct record that the create/edit/view screens for Story in X changed, and the issue payload itself doesn’t contain configuration history. To truly confirm whether the Story screens in project X changed, you’ll need to look in Jira’s configuration and audit log.

Here’s the fastest way to check this yourself.

And then Rovo proceeds to explain how to look at the audit log, if I have admin access.

Not being able to view Jira configuration data, even when running as an admin account, is one of the biggest limitations for me in Rovo so far. I also have found it doesn't have access to recent Jira release notes unless I explicitly ask it to search for them, so questions about new functionality don't work.

[Kristen Roth]

@Savannah Ehrhardt thanks for flagging that it's not working for you! I'm going to remove the first prompt suggestion/bullet in Tip #2 and do a bit more investigation. Do the next two work for you? They did both work for me. 

[Maor Levinas]

@Kristen Roth Same for me 

[Savannah Ehrhardt]

@Kristen Roth yes, the others work for me.

[Kristen Roth]

Thanks, @Maor Levinas ! I've removed that prompt suggestion from the page since it hasn't been working for everyone.

[Savannah Ehrhardt]

@Kristen Roth it still seems to be there?

[Kristen Roth]

@Savannah Ehrhardt I've refreshed & updated again. Hopefully it's ok now? 🤞