Before you start

  • An Atlassian Cloud site with Jira and access to Rovo agents.
  • An administrator authorised to install apps on your site.
  • Permission to view the Jira tickets and comments you want to review.

Rovo availability and controls depend on your Atlassian subscription and organisation settings. Ask your administrator to verify access. The app does not require you to enter passwords or API tokens.

Install the app

  1. Ask your Atlassian site administrator to locate NexiStack First Line AI through the installation or distribution link provided for your app version.
  2. Select the intended Jira Cloud site and review the requested permissions and policies before confirming installation.
  3. Complete any Atlassian consent steps and verify that the agent appears in Rovo’s agent selection.

If the app is not yet available in your app catalogue, contact Nexi Stack for availability and the appropriate installation route. A public Marketplace listing link will be added when available.

Set up and verify access

This version has no separate app settings screen. Jira permissions and Rovo access are managed in your Atlassian environment.

  1. Verify that intended users have Rovo access.
  2. Open a non-sensitive test ticket directly in Jira to confirm access.
  3. In Rovo, select NexiStack First Line AI and ask it to explain that ticket.
  4. Compare the result with Jira. Check that restricted information remains unavailable to users without access.

Do not change user permissions solely to make a test pass. Use your established access review process.

Your first conversation

  1. Open Rovo Chat where it is available in your Atlassian product.
  2. Select NexiStack First Line AI.
  3. Choose a conversation starter or type: Help me understand NSP-126.
  4. Replace the example key with a ticket you can access.
  5. Review the answer and open the original Jira ticket to verify relevant details.

For troubleshooting, include the affected service, symptoms, error message, impact and steps already attempted. Do not include credentials or unnecessary personal information.

Example use cases

Review a ticket

Explain NSP-126: what is the issue, current status and priority? The action reads those fields and the description when Jira permits access.

Understand recent discussion

Summarise the latest comments on NSP-126 and distinguish suggestions from confirmed fixes. The action retrieves one page of up to 20 comments, newest first.

Prepare a support request

Help me draft a support ticket for a VPN connection failure. It started this morning; restarting did not help. Review the draft and submit it yourself through your organisation’s support channel.

Explore available guidance

Find guidance for this support request. Search and source access depend on tools available to Rovo. If evidence is unavailable, the agent should explain the limitation rather than invent sources.

Permissions and data access

The current app manifest declares read:jira-work, write:jira-work and read:jira-user. The implemented ticket action performs read requests as the authenticated user; it has no write action. The declared write permission does not mean this version can create or update tickets.

Review the actual installation consent screen for the version being installed. See the security policy for access controls and the privacy policy for data handling.

Coverage and limitations

  • Reads ticket summary, description, status and priority.
  • Retrieves up to 20 latest visible comments in one request; older comments are not automatically paged through.
  • Descriptions are limited to 20,000 characters in their structured representation; each comment body is limited to 4,000. Partial content is flagged.
  • Does not retrieve attachment contents.
  • Does not include a dedicated Assets lookup action.
  • Does not create, edit, comment on or delete tickets.

AI-generated guidance is not a substitute for administrator approval or incident response procedures.

Troubleshooting

Agent not visible

Check the selected site, installation status and Rovo access with your administrator.

Ticket unavailable

Check the key and open the ticket directly in Jira. The app does not bypass issue security or fall back to app-level access.

Authentication or user context error

Complete any Atlassian consent request. If the error persists, ask your administrator to investigate and contact support with the error category.

Comments could not be retrieved

A failed request does not mean there are no comments. Check Jira directly and retry. If only 20 comments are returned, older comments may exist.

Incomplete response

Check coverage and truncation notices, then review the source ticket. Provide a focused follow-up question.

Uninstall and request help

An authorised administrator can remove the app through Atlassian’s connected-app management for the relevant site. Removing the app does not delete your Jira tickets or comments.

The implemented action does not persist ticket bodies in an app database. Rovo conversations and platform logs are governed by Atlassian’s controls. Uninstallation does not guarantee immediate deletion of platform records or support correspondence. Contact your administrator and Nexi Stack support for data requests.