Comments
-
Hi @Charles Brooks You can't export data directly into a CSV using Jira automation. Automation rules don't support writing to files like that. What I did instead was use a small Python script that connects to Jira using the REST API. It runs a JQL query, grabs the fields I want (like issue key, summary, status), and then…
-
Hi @[deleted] If you're using LDAP authentication with Bitbucket (Stash), user management like creation or removal should be handled directly through the LDAP directory not via Jira or Bitbucket APIs. These tools treat LDAP users as read-only. That said, you can still remove or restrict user access using ScriptRunner in…
-
Hi @Sai Audithya Sarvabhotla When using the Zephyr API to add test steps, this error usually means the account used in the API call (via the JWT token) doesn’t have the necessary permissions in that Jira project even if Jira shows that EDIT_ISSUES is granted. Here’s what to check: - Make sure the JWT token is signed with…
-
Hi @David Schneider This issue looks related to Velocity template rendering in Jira Data Center 10.7.1. The placeholders like $esc.html($server.name) usually appear when Jira fails to render field values due to escaping or backend data issues. Steps to identify the root cause: 1. Run the SQL to check if the mail server…
-
Hi @Ashmita Mishra Yes, this is possible with Jira and GitHub integration. Here's how you can achieve it: 1. First, tag all the issues with a Fix Version (example: v1.0.0) 2. Then, go to Jira → Releases → Create the version (v1.0.0) → Release it when ready 3. Now set up an Automation rule: * Trigger: Version Released *…
-
Hi @Hunter Lardy Yes, this is a known limitation in Jira — even though it’s not clearly mentioned in the documentation. A single project or space can be linked to **maximum 15 Jira Teams**. That’s why you’re getting the error when trying to add Team #16. To fix this: 1. Go to https://teams.atlassian.com 2. Unlink the…
-
Hey, I’ve seen this kind of email before and totally get the confusion. Even if you already have Jira products running and paid, this kind of message usually pops up when **one specific subscription fails** — in your case, it looks like the payment for **Jira Product Discovery (monthly)** didn’t go through. Why it…
