Gor Greyan Expert

Hi @Jessica Fallon Welcome to the Atlassian Community! project in JCM AND (parent IN (JCM-71) or issuetype IN subTaskIssueTypes()) AND statusCategory != Done I tried this one and it worked. Check also this one.

Hi @Jonathan Porta That stack trace is from Meta-Inf’s Email This Issue (JETI) app, and the error means JETI couldn’t resolve any recipients from what you configured, so it aborted the send. A Labels-type custom field doesn’t contain email addresses or users, so JETI’s recipient resolver finds nothing and throws…

Hi @Lupita de Alba Welcome to the Atlassian Community! I agree with @Trudy P Claspill If you can, please provide entiry rule. Also, I found this article about that error. https://support.atlassian.com/automation/kb/all-rules-are-failing-to-be-executed-due-to-the-error/ Also, if you want to reopen non-logged ticket, you…

Hi @Corey Hemingway Maybe it can be for the following reasons: - Triggered by multiple rules (a project rule and a global rule), or - The rule’s scope includes multiple projects, or - It’s re-triggering itself due to “Allow rule trigger” being enabled. Please also check these points.

Hi @Dan W Glad that solution works. You can also use this website for crone creation. I am creating crones from here, and it wis orking in Jira. https://www.freeformatter.com/cron-expression-generator-quartz.html

It’s amazing how a single smell can take you back decades in an instant. :D For me, it’s the smell of freshly baked lavash. Every time I catch that scent, I’m right back in my grandmother’s village :), standing by the tonir as she pulls out warm bread with her bare hands. The air was thick with smoke and laughter, and…

Dear @Andres Cappiello Try to compare issue metadata side-by-side Pick one Epic that disappears when Done, and one that stays. Compare fields: Start date, End date / Target end, Fix version, and any custom date fields your plan uses. See if one has a missing or outdated date that causes it to fall outside the timeline…

Hi @Dan W You’re right—Jira Automation (Quartz-style cron) wants literal day names (MON–FRI) or the Quartz numbers where 2–6 = MON–FRI. Using 1–5 means SUN–THU, which fails (is wrong). Check please this doc: https://confluence.atlassian.com/jirasoftwareserver/constructing-cron-expressions-939938814.html

Hi @julie_calboutin Welcome to the Atlassian Community! Let's do some fixes. In the 2nd instance, which is reciever: Edit the rule trigger: Trigger: Incoming webhook In the Create issue action, pull values from the webhook using {{webhookData}}: Summary: {{webhookData.summary}} Description: {{webhookData.description}}…

Hi @Nihar Sharma For the Reporter and assignee, it is possible I think like this. Reporter <span>project = "PROJECTKEY"</span>Then, in the Issue Navigator, make sure to display the Reporter column.You can export to CSV (Issues → Export → CSV (All fields)) and collect all unique reporters per project. Assignee <span>project…

Hi @Wakil BENAMOUR If you write labels not in (ano_US), it returns all tickets that have la abel and it is not ano_US. For the correct one, you should use labels not in(ano_US) or labels is empty, for including also tickets without labels.

Dear @Andres Cappiello I think we can do these checks. Verify the Resolution for the disappearing issue: Open the Epic in Jira. Scroll to the Resolution field → if it set something like “Done” or “Fixed”, it’s truly resolved. If the clone (that still shows) has no Resolution, that explains the difference. Test: Remove the…

Dear @Maksims , When an Atlassian account becomes managed, Atlassian legally treats the organization as the data controller. This means: Atlassian cannot directly edit or disclose your admin’s name or contact details without authorization. The “Contact your admin” link is intentionally anonymized — it triggers an internal…

Hi @ Arpit Gupta - You should claim all remaining users under the domain Go to admin.atlassian.com → Organization → Domains → Claimed accounts. Select mydomain.altostrat.com and click Claim accounts to include all users. Re-provision the users After claiming all accounts, delete the existing External / Deactivated users…

Dear @ Arpit Gupta -Go to admin.atlassian.com → Directory → Managed accounts and check the account type. -If it’s marked as External, you’ll need to: Claim or verify the user’s email domain under Organization settings → Domains. Once the domain is verified, transfer or claim the user so that Atlassian treats them as a…

Hi @Andres Cappiello Welcome to the Atlassian Community! I found this article in Community, where it is said that: By default, Advanced Roadmaps doesn’t display issues completed in Jira Software more than 30 days ago. You can adjust this timeframe to suit your planning needs. To adjust the number of completed issues…

Hi @Maksims Welcome to the Atlassian Community! It indicates, that your Atlassian account has been converted into a Managed Account.This happens when your organization (the domain owner) claims ownership of all Atlassian accounts associated with that email domain. When this occurs: Profile information like name, job title,…

Hi @ Arpit Gupta Welcome to the Atlassian Community! The user shows as Deactivated and External (non-corp) because their account was likely unassigned or deactivated in the IdP, and SCIM synced this status to Atlassian. To reactivate: Check IdP (Okta/Azure AD/Google Workspace): Make sure the user is active and assigned to…

Hi @Glanz _Huy_ Nguyen Welcome to the Atlassian Community! First of all try: Hard-refreshing the page (Ctrl+Shift+R). Logging out and back in. Using Jira in an incognito/private browser window. Clearing your browser cache or switching browsers temporarily. If this works, it’s a caching issue. If not, inform us, see what…

Dear @Cynthia Borot Yes, in the Free plan, Jira only gives access to: The basic Timeline (or Roadmap) feature, which is auto-calculated from issue Start and Due dates. You cannot configure global project dates or modify the visible date range manually. You also don’t have access to Advanced Roadmaps, where date field…

Hi @Cynthia Borot Welcome to the Atlassian Community! The project start and end dates in Jira’s timeline are automatically based on the earliest and latest issue dates.To adjust them, edit the Start date and Due date of your highest-level issues (Epics or Initiatives).If you’re using Advanced Roadmaps, you can also…

Hi @Erick Pacheco Please try this link. https://admin.atlassian.com/o/create

Hi @Philip Ng Try this smart values. After the trigger, put 2 compare conditions. 1.{{fieldChange.toString}} contains released 2. {{fieldChange.fromString}} doesn't contain released <span>Together these ensure the rule only fires when </span>released<span> is </span><em data-start="1054" data-end="1067">newly…

Hi @Roopesh Sontenam Please try this way. Ensure that the ROVO integration is connected to your JIRA instance. In ROVO, go to Settings → Integrations → JIRA. Confirm that your workspace has the correct authentication (usually via OAuth or API token). Then. In JIRA, go to Project Settings → Permissions for the APRICOTBSC…

Hi @Caitlin Brown Welcome to the Atlassian Community! You’re getting “data was not an array” because those two custom fields (Objective = customfield_11710, KR = customfield_11402) are multi-select fields in Jira. For multi-selects, Jira expects an array of option objects, not a single object/string. Try this one. {…

Hi @Ron Aisen You can do a bulk change via Automation. Add Resolution filed on the Edit Screen of the issue types. Create Automation. Trigger - Scheduled. Write the JQL, which tickets should be changed. Action. Edit fields --> Resolution, and select the new resolution.

Hi @Erick Pacheco Welcome to the Atlassian Community! Please see these articles. https://support.atlassian.com/jira-service-management-cloud/docs/add-an-organization-to-a-service-project/ https://support.atlassian.com/jira-service-management-cloud/docs/add-a-customer-to-an-organization/?utm_source=chatgpt.com

Hi @Ryan Broadhurst I think we can do it via 2 automations, as variables are not being worked in the sub-tasks when we add a branch. Would you like me to provide a possible solution via 2 automations? With the first automation, we will capture the day difference between old and new days, and via the 2nd automation, we will…

Dear @Joe Palmer Yes, here is the screen. Also, this is the lookup jql project = INC AND "Provider Name" = "{{issue.Provider Name}}" AND key != {{issue.key}} and issuetype = incident and reporter = Fatal_Monitoring and statuscategory != done ORDER BY created ASC

Hi @Joe Palmer Welcome to the Atlassian University! I have this automation, which finds a ticket where the Provider Name field is the same, it finds that first ticket and links the rest tickets to that one. See, if this will help, we can do some adjustments.