Gor Greyan Expert

Hi @Dilip Kumar Shrivastwa Welcome to the Atlassian Community! Please try this one. import os import requests from requests.auth import HTTPBasicAuth def create_remote_link(issue_key, remote_link_url, remote_link_title): jira_base = os.getenv("JIRA_BASE_URL") # https://yourcompany.atlassian.net jira_user =…

Hi @Michael Kobert No, nothing is missing — the “User has access / no access” condition is part of the legacy automation, and it’s not available in Jira Automation yet. You can work around it by checking if the commenter is in a specific group or project role. Hopefully, Atlassian will bring this condition in a future…

Dear @Zofia Subocz You are very Welcome!

Dear @HQRAZAHS - Yes, the Epic issue type is locked at Level 1 in Jira and can’t be moved below another issue type like Feature. Any new hierarchy level you create (Initiative, Capability) is always placed above Epic. - The structure of Version 2 is technically possible in native Jira if it is Premium or Cloud. However,…

Dear @[deleted] Thanks for providing that direct answer. What did you find wrong or old in my answer, for continuing this topic? It wasn’t a copy-paste — it was written from official Atlassian sources to support and expand on your point. Have a good weekend, brother :)

Dear @Zofia Subocz Great! Also, kindly ask you, if this helped you, accept the answer, in order for other community members to also know the solution.

Hi @HQRAZAHS 1. Recommended Hierarchy is version 2: it provides: Clearer structure and aligns with SAFe. Better for reporting and roll-ups. Avoids mixing direct Story/Feature under Epic. 2. Impacts of Change: Parent-child links lost (Initiative–Epic–Feature). Automations using parent/epic link fields will break. JQL…

Hi @Nivi Mor Yes, you are right, Nivi — that behavior happens because API tokens used with Basic authentication don’t use scopes at all. Scopes are only enforced when you’re using OAuth 2.0 authentication (for example, when an external app integrates with Jira Cloud via the Atlassian platform). In that case, the access…

Dear @Zofia Subocz After trying, please let me know if this worked or not.

Hi @[deleted] Just expanding on your answer with supporting references, so future readers have the full context.

Hi @Mai Miyamoto According to Atlassian’s official documentation, automation audit log entries in Jira Cloud are stored for 90 days (approximately 3 months). Entries older than this are automatically removed and cannot be recovered. You can check this doc:…

Hi @Michael Roalkvam Welcome to the Atlassian community! - Jira Server 9.12.28 cannot be applied if your Server license has expired. Atlassian policy: You can keep using Jira after license expiry, but you cannot upgrade to any version released after your maintenance end date.…

Hi @Ali Ali You’re on the right track! Jira Cloud Migration Assistant (JCMA) can move your workflows, fields, and issues — but a few best practices will help you preserve everything cleanly: Custom Workflows & Transitions Native workflows, statuses, and transitions migrate automatically with JCMA. Custom triggers or…

Hi @Thu Nguyen That’s great to hear — thank you for confirming! 🎉 Yes, in Team-managed projects, Jira sometimes handles certain fields (like Story point estimate) differently under the hood. When using automations, referencing the field ID instead of the display name ensures Jira maps the field correctly, especially if the…

Hi @Biswash Lamsal Let's check the following points: 1. Check board estimation settingsGo to Board → Configure → Estimation → make sure Time tracking is selected. 2. Verify the “Time tracking” field on issuesEnsure the Time tracking field (Original + Remaining estimate) is visible on issue screens. 3. Tempo logging…

Hi @Regina Ann Richard Great. Also, please accept the answer, if it helps, dear Regina :)

Hi @Wyman Yan Did you check the "Assign issue" permission in the Permissions section? Are you involved in any of the roles, groups associated with that permission?

Hi @Thu Nguyen Did you receive an error message? Could you please share the audit log?

@Rachel Tang, the new Admin Hub sounds like an incredible resource — it’s great to have a centralized space for updates, best practices, and learning materials tailored to Jira administrators. :) I really appreciate the effort that went into creating this and look forward to exploring the features and insights shared here.…

Hi @Laura Pellizzari You are very welcome. You don’t need indentation for Structure formulas—the parser ignores it. What does matter is: single = (not ==) commas between helpers inside With Exactly one colon : to end the whole With block using the right link collection name (workItemLinks in your default column) WITH…

Hi @Biswash Lamsal What I’d suggest you check/do: In the board for your Scrum project: go to Board → Configure → Estimation (or Board Settings → Estimation) and check that "Time Tracking" is enabled. https://support.atlassian.com/jira-software-cloud/docs/configure-estimation-and-tracking/?utm_source=chatgpt.com Deleting…

Hi @AdnanFakhar Training Material Firstly, change the URL host and pathUse your Jira site, not the Atlassian gateway, and the Agile API path:https://<your-site>.atlassian.net/rest/agile/1.0/board?projectKeyOrId=BUN. https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/?utm_source=chatgpt.com Keep Basic…

Hi @Marc -Devoteam- Yes, you are right, thanks for the correction.

Hi @timothy_higgs_extern Your “Edit Issue Field → Labels” action should not be inside the “For: Parent” branch — it must be outside, so it targets the issue that triggered the rule (the new child). Please confirm that it is outside.

Hi @Joseph Ambrosio Welcome to the Atlassian Community! Firstl,y check the permission: Go to Project settings → Permissions. Look for Manage Watchers. Ensure your role (or group) is listed.

Hi @deepthy g Is the Team field comes from the Advanced Roadmap? If yes, please try this one: Trigger:When: Issue assigned Condition:If: Assignee = any specific user Action → Edit issue fields → More options Paste this JSON: { "fields": { "Team": { "id": 12 } } } If it is a customfield, try this one: { "fields": {…

Hi @Thu Nguyen Welcome to the Atlassian Community! In Team-managed projects, the field “Story point estimate” only exists if estimation using story points is enabled.If estimation is turned off or changed (for example, switched to “Time tracking”), Jira will throw that error. If it is enabled, try this one in Additiona…

Dear @SURAJ TIWARI Get it. It is Maintenance windows occur daily between 1 am and 3 am in the timezone of the server your product is on. You can check this doc for details: https://support.atlassian.com/organization-administration/docs/keep-track-of-maintenance-windows/ You can also contact the support here: so that they…

Hi @SURAJ TIWARI No, there are no ongoing incidents; you can check the Atlassian Status Page. https://jira-software.status.atlassian.com/ What issue do you have?

Dear @LPK Yes, not all materials have been updated yet. After you move to Cloud, you’ll start seeing “Work” instead of “Issue” across the interface. Following, you can see the screen in our Cloud.