| Summarize release |
/summarize-release |
/summarize-release for [release name]. |
Rovo will generate a Release summary which will include the health of the release, and more details like:
- Number of work items in the release and their status
- Related blocked work
- Overdue work
This skill is designed to work with the Releases also known as Fix versions in Jira. How to set up releases
|
Apps:
Jira
Plan
Any
Collections:
Software
Permissions:
User
|
| Create release |
/create-release |
/create-release in [space name] for our latest app update. |
Rovo will create a new release based on the description you provided, or it will infer a release based on the work items available in your backlog.
This skill is designed to work with the Releases also known as Fix versions in Jira. How to set up releases
|
Apps:
Jira
Plan:
Any
Collections:
Software
Permissions:
User
|
| Draft release notes |
/draft-release-notes |
/draft-release-notes for [release name] make sure to highlight the improvements to performance |
Rovo will write release notes for the release name you provided. It will consider any additional instructions relating to what you’d like it to cover in the release notes. Once Rovo finishes writing, you can choose to directly publish the release notes to Confluence.
This skill is designed to work with the Releases also known as Fix versions in Jira. How to set up releases
|
Apps:
Jira, Confluence
Plan:
Any
Collections:
Software
Permissions:
User
|
| Write status update |
/write-status-update |
/write-status-update for [work item] OR
/write-status-update for this project [Atlassian Project] over the past week |
Rovo will generate a status update that covers recent activity, highlights, and flagged risks. If you’re using Atlassian Projects, you’ll have the option to publish the update directly to the Status updates view in the Projects directory. |
Apps:
Jira, Confluence, Projects (optional)
Plan:
Any
Collections:
Teamwork
Permissions:
User
|
| Update work items |
/update-work-items |
/update-work-items [work item key] and change the assignee to [@name].
OR
/update-work-items [work item key] and change the status to done.
OR
/update-work-items on this board [link to Jira board] based on this video [link to Loom video] |
Rovo will make the desired change to the work item you provided (or a work item you’re viewing). Rovo can update the following fields of a work item:
- Status
- Assignee
- Description
- Environment
- Summary
- Comment
- Labels
- Parent
- Priority
- Due date
|
Apps:
Jira
Plan:
Any
Collections:
Teamwork
Permissions:
User
|
| Explain next status |
/explain-next-status |
/explain-next-status for this work item.
/explain-next-status for ABC-123.
This skill can also be triggered directly from the Status menu on a work item which will not require you to type a prompt.
|
Rovo will provide a list of available statuses for a provided work item (or work item that’s being viewed). It will also explain any requirements that need to be satisfied in order to transition to any of those statuses, with the goal of helping users progress their work items through workflows. |
Apps:
Jira
Plan:
Any
Collections:
Teamwork
Permissions:
User
|
| Get data insights |
/get-data-insights |
/get-data-insights about how many deployments occurred in each environment type in the last 30 days. |
Rovo will generate a chart and provide insights based on inputs you provide. You need to specify exactly what you want insights on, like the Jira space name, the user, or teams that you're interested in. For now, the skill can’t provide results for broad queries like “tell me about my team”. See exactly what you can track with this skill below this table.
Note: this skill doesn't yet support custom fields, or sprint and board data. So you might not be able to map your insights to a specific sprint or board.
|
Apps:
Jira, Jira Service Management, Customer Service Management, Goals, Bitbucket
Plan:
All paid editions
Collections:
Platform
Permissions:
User
|
| Find Jira settings |
/find-jira-settings |
/find-jira-settings to help me configure workflows. |
Rovo will provide instructions on where to go to find specific Jira admin settings and a direct link to the right settings page.
Note: this skills doesn't yet read your context, so you can't ask it about things on your screen.
|
Apps:
Jira
Plan:
Any
Collections:
Teamwork
Permissions:
App admin
|
| Manage Jira permissions |
/manage-jira-permissions |
/manage-jira-permissions and help me understand why [@name] can’t access these work items [work item key(s)]. |
Rovo will use its knowledge of permissions and access in your organization to help you troubleshoot on behalf of your users. |
Apps:
Jira
Plan:
Any
Collections:
Teamwork
Permissions:
App admin
|
| Assist Jira plans |
/assist-jira-plans |
/assist-jira-plans and help me add dependencies between work items |
Rovo will help with variety of tasks that help you manage and update a Jira plan including:
- Analyze and provide a summary of a plan’s progress.
- Add work items to a plan
- Add dependencies between work items
- Remove dependencies between work items
- Enable release
- Create space level release
- Create program board
- Retrieve and show program boards
- Delete program board
- Update work sources by adding or removing Jira spaces or boards
This skill is designed to help you work with Jira plans. More on Jira plans
|
Apps:
Jira
Plan:
Premium or Enterprise
Collections:
Teamwork
Permissions:
User
|
| Search Assets data |
/search-assets |
/search-assets show me all the laptops assigned to me |
Rovo searches the Assets database for relevant schemas, object types, and objects and determines the most appropriate data to match the query. It will return the information in the from of a text response. |
Apps:
JSM
Plan:
Premium, ENT + STD from January
Collections:
Service Collection
Permissions:
Inheriting Assets Permissions (users will only be able to fetch data that they have access to in Assets UI)
Note: as Assets are being rolled out as a separate App these requirements will change.
|