Hari Krishna Community Champion

Rovo can help partially, but it cannot fully automate this use case. Rovo can search for a specific text like scew123 and tell you which pages contain it, if you ask it directly. This is useful for manual checks or investigations. However, Rovo cannot automatically scan all pages in a space, compare pages for duplicates,…

Hi @Darius Collins , The JIRA Time Tracker app does not fully support Jira Dark Theme yet, so some parts still show light colors. Jira’s dark theme does not automatically apply to Marketplace apps, and I think currently no setting or workaround to fix this from Jira’s side. Only the app vendor can update it.

Hi @Yanick.Robert , You can’t add a calendar to a JSM space. JSM does not support calendars like Confluence does. In JSM, SLA calendars (working hours, holidays) only available If you need a real calendar you can: Use Confluence plus Team Calendars and link it to the JSM project So you’re not missing any option calendars…

Hi @Christian Wolf , This cannot be fully automated using Rovo alone. Rovo can read and summarize pages, but it can’t scan all pages in a space, compare duplicate text across pages, and then link Jira issues automatically.

I think you may now get it, Only jira admin can archive the projects.

Hi @srujana_garneni , I think it may be because of this reason, If the Archive option is missing, it's typically not because the feature is absent but due to insufficient permissions, May I know do you have the jira admin permission. FYI : Only jira admins can archive the projects

Hi @srujana_garneni , You can directly go to the projects -> check for the project -> click on the 3 dots, there you can see the archive option, or else you can refer this document Archiving a project | Administering Jira applications Data Center 11.3 | Atlassian Documentation https://share.google/8TtlafZfQJ2033bFa

Add the required Jira fields directly in the JSON body of the Create a new issue (V3) action. Copilot does not map fields one-by-one. You must pass them manually using field IDs. Example for Security Level = Internal: { "fields": { "security": { "id": "xxxxx" } } } For custom fields: "customfield_12345": "value" Use field…

Hi @Christopher Proulx , This happens because Jira thinks you’re trying to create a new project, not import issues. In your CSV, there is likely a Project Name Key column. When Jira sees that, it tries to create the project again and fails because it already exists. fix: Remove Project Name / Key columns from the CSV…

Hi @Holte_ Henrik , This isn’t something you can fix yourself. What likely happened is that during the move from standalone Opsgenie to JSM Premium, the old Opsgenie subscription was blocked or deleted, and your user is now stuck linked to that old account. That’s why you can’t log in or create a new Opsgenie account with…

Hi @Michael Brändel , The Site Optimizer is intentionally conservative in how it identifies unused fields. It does not rely only on whether a field appears on screens or has current values in a project. A field will be kept by the optimizer if it is referenced anywhere, such as in workflows (conditions, validators,…

Hi @Patrick Schneider , This is not possible using Jira Automation. Because Stagil Tables are table-type custom fields, and Jira Automation does not expose their changelog data. Because of this limitation, smart values like {{changelog.customfield_xxxxx}} will always return empty after a table update.

Hi @Mahima - Optimizory , Use the List view or All work, when you need accurate results based on filters or JQL The Summary panel cannot be customized with JQL and will only update once there’s broader project activity like status changes, recent updates, etc. If you need reporting based on JQL, use: Filters Dashboards…

Hi @Venkat Jira Admin , Jira boards are based on filters. The issue occurs because the board filter is not shared with the new users, which is why they cannot see the boards. Sol: Go to Board settings Click on the Filter name Share the filter with: The relevant project role, or The required user group Ensure the user has…

Hi @Gade Chaitanya , This means either the board no longer exists or you don’t have access to it. Most likely, your permissions were removed. Please contact the Jira admin and ask them to give you access to the project or board. If they confirm you already have access, then the board may have been deleted or renamed and…

Hi @Jason Michaud , Jira cannot password-protect or selectively lock individual fields or attachments with audit logging for all viewers. Apps like Secure Fields are limited (for example, assignee-only access), and attachment-level password protection is not supported out of the box. What teams usually do: Use a…

Hi @Thanh Le , The grey space comes from the Forge modal container itself. Unlike Connect, Forge does not allow you to control or remove the outer spacing of a modal. There’s no direct fix right now. The only try some workarounds: Adjust your inner layout so it looks better inside the modal Or avoid using a modal and use a…

Hi @Nick Braciszewski , Jira is rejecting the request because your project/issue type has mandatory fields, and Copilot is only sending Project + Issue Type. The other required fields are missing, so Jira returns the 400 error. Try: Check which fields are required for that issue type in Jira, then add and map those fields…

Hi @George Abdo , When pages are created or updated via Automation or Rovo, Confluence records the automation user as the creator/updater, not the person who triggered it. Because of that, Analytics can’t accurately report “who really created or updated” pages in these cases. At the moment, there’s no native way to…

Hi @Heidi Hendry , No — OOTB Rovo Agents can’t be disabled, deleted, or hidden individually right now. They’re always visible to users who have access to Rovo. What you can do is create custom Rovo Agents for your use cases and guide users to use those. Even if an OOTB agent is visible, actual actions are still blocked by…

Hi @G P N , For this kind of requirement, ScriptRunner’s Mail Handler is the better fit. The built-in Jira (Enterprise) email handler is really meant for simple scenarios only — things like creating a new issue from an email or adding a comment when the issue key is already in the subject. Once you go beyond that, it…

Hi @manoj.biradar , The Alerts LIST API intentionally returns a lightweight response and does not include description and entity fields. Those details are only available via the GET alert by ID endpoint. This is a design choice to keep list responses fast and reduce payload size. At the moment, there’s no way to include…

Sorry for the misunderstanding. The solution was proposed by me based on my own calculations; it was intended as an overview and not a complete rule. I apologize if it came across as inappropriate. I will be more careful going forward and ensure better clarity next time. And thanks for the advice. Thank you.

Yes, that’s correct. Workflow validators are evaluated only during workflow transitions. They don’t block users while typing or saving field values, but they prevent the issue from moving to the next status if the field value doesn’t meet the required format. So in practice: Users can enter any value in the field The…

Hi @Corey Hampton , This usually happens when Confluence is no longer connected to the Production Jira site, even though you still have admin permissions. The Create Work Item macro only shows Jira sites that are actively linked to Confluence via an Application Link / Jira integration. If Production suddenly disappeared,…

Hi @Skye DeStefano , Unfortunately, this is a known limitation/bug in Confluence Data Center when using the TOC macro in the sidebar, and there is no supported fix at this time. As documented in CONFSERVER-43090, the sidebar TOC generates anchor links that do not resolve correctly, which results in the “page not found”…

Hi @Maninder Singh , This error usually appears when there is a billing or subscription issue on the Atlassian site, even if other products are still accessible. Please check the following: Go to admin.atlassian.com → Billing → Subscriptions and verify there are no failed or overdue payments. Make sure your site has an…

Hi @Vanessa Torres , This is a known and expected issue when upgrading plugins from Jira 9.x to Jira 10.x. The missing dependencies you listed (oauth2-pageobjects, atlassian-lighthouse-plugin-wired-tests, pats-test-plugin) are internal test-only artifacts used by Atlassian. They are not published for third-party plugin…

Hi @Yasuda Yuya , This is not expected behavior and is most likely a backend issue with Confluence Analytics exports, not a configuration problem on your side. When a CSV export suddenly drops from thousands of pages to only a few hundred, it usually indicates a data processing or export limit issue introduced during a…

In Jira Automation, setting the request type / work item type cannot be done by updating a custom field alone. The value you’re setting (customfield_10010) is just storing data, not defining the issue type. To create a linked issue with the correct type in another project, you must explicitly set: project issuetype (work…