Gor Greyan Expert

Hi @Laura Pellizzari Thanks for the follow up: Please try this one WITH markdown(issue) = CONCAT( "[", IF issue.status.category = "Done" : "~", issue.key, IF issue.status.category = "Done" : "~", "](", issue.url, ")" ), /* Return the issue on the “other side” of a link */ other(link) = IF link.source.key = key :…

Hi @Kumar_ G Sunil Please try the following script in the post-function, putting it before the re-index step. import java.time.* import java.util.* import com.atlassian.jira.component.ComponentAccessor def cf = ComponentAccessor.customFieldManager.getCustomFieldObjectByName("Your Date Field") def newDate =…

Hi @Ryan Willms Did you editing the "Box" field, or it is being edited via another automation?

Dear @Caitlin Brown Glad that it help, thanks for informing.

Dear @Robin Yes, it does require administrator access in both organizations. You must be an org admin in the source (to start the copy). The person on the target side must also be an org admin (to accept and apply it).

Dear @Robin Great, let me know, if you have any questions.

Hi @Ardalan Sepehri Starting from the morning, Atlassian has an ongoing Incident, regarding different part of the Jira. You can follow up on this via the Status Page. https://jira-software.status.atlassian.com/

Hi @Ryan Willms Could you please provide screenshot from the Audit Log of the mentioned automation?

Hi @Robin Welcome to the Atlassian Community! Yes, you can migrate or export your projects from one Jira account to another using this built-in tool in Jira. You can refer to this page for details.

Dear @Andreas Dahlström Got it, yes, the best is to open a support ticket.

Dear @Andreas Dahlström For most users, the correct record should be: bounces.mail.atlassian.net not bounces.mail-us.atlassian.net. Did you also try this record? If the issue persists, the best is to create a support ticket on Atlassian to fix the incorrect CNAME requirement on their side. Open a ticket via:…

Dear @Chris Vernon Glad that it works. Also, please accept the answer :) Have a good day, Chris!

@Chris Vernon Thanks for the information. Let's do that by creating a variable. Befor the branch, put Create variable: Name: oldGoLive Smart value: <span> {{fieldChange.from}}</span>Then, inside the branch, edit the field and set {{var.oldGoLive}}.

Hey @Chris Vernon Got it, the log confirms the smart values resolve correctly, so the issue is likely that the automation is editing a related issue rather than the trigger issue. When you use a “Branch rule / related work items,” the smart value {{fieldChange.from}} may no longer exist in that scope. Try this one:…

Hi @Andreas Dahlström Did you try to delete and remake the TXT record completely? After that, you should wait for the propagation. Also, look at this Troubleshooting page, maybe this will help. https://support.atlassian.com/organization-administration/docs/troubleshoot-custom-domains/

Hi @Chris Vernon Welcome to the Atlassian Community! There is no need to format the field. Use the following smart value, which already returns the raw ISO date (yyyy-MM-dd) that Jira expects. {{fieldChange.from}}

Hi @Sofiia Welcome to the Atlassian Community! It means Automation does not yet have authorization from your GitHub organization to access its repositories. Go to GitHub → Organization Settings → Third-party access. Authorize the Atlassian Automation app During the authorization, select the relevant organization and…

Hi @Angelie Stephens Great idea to share one of our rituals :) Every second Wednesday, we hold a short “learning exchange.” Each person shares one quick insight — a new tool, article, or even a mistake that taught them something valuable. It’s a light way to keep growing as a team and spark curiosity.

Hi @Anna Menzel Welcome to the Atlassian Community! Did you try to delete the organization? Dear @Prachi Bolar Could you please look at this?

Dear @Anna Guliaeva Yes, maybe for the MacOS is now also not available for downloading. For the iOS it is available. My suggestion is to use the web version, instead.

Hi @Anna Guliaeva Welcome to the Atlassian Community! Check this one. https://apps.apple.com/us/app/jira-cloud-by-atlassian/id1006972087 But also, this documentation said that support for that app is stopped, and new updates will not be provided and the recommendation is to use the web version.…

Hi @Sneha Joseph Despite what @John Funk suggests to check, which can be one of the reasons, please also check these points. User has both “Assign Issues” and “Assignable User” permissions Workflow transition doesn’t restrict assignments(Properties) User is an agent (if this is a Service Management project)

Hi @Beth Jokhio In Team-Managed Jira projects, the “Remove done items after X days” option currently applies only to Kanban boards, not Scrum boards — which is why you don’t see the three-dot menu on your “Done” column in Scrum. In Scrum, Jira’s cleanup logic isn’t “remove after X days,” but rather “remove when the sprint…

@Nihar Sharma Got it, but I think Jira does not have such an easy way to view the mentioned criteria and their activities.

@Beth Jokhio Both TTU-60 and TTU-127 are in a green (Done category) status.However, Jira’s Summary Donut only includes issues that entered the Done category within the configured retention period (14 days by default). I think,TTU-127 was completed before that threshold, so it’s automatically excluded even though its status…

You can find it by clicking the three dots next to the Done column. You will see "Remove Done Items after X days". Enter there, you can change it.

Hi @Beth Jokhio Welcome to the Atlassian Community! The “Summary” donut chart on a Team-Managed Jira project does not show a full count of all issues.Atlassian’s documentation confirms that it only includes items updated recently: Only “Done” issues completed in the last 2 weeks appear in the Summary Donut (or “Status…

Hi @Laura Pellizzari I think you should filter the link collection before you group/map it, keeping only links where the “other side” of the link belongs to your target project. Try the following one. WITH markdown(issue) = CONCAT("[", IF issue.status.category = "Done": "~", issue.key, IF issue.status.category = "Done":…

Hi @Paul Cooper Welcome to the Atlassian Community! In some Jira configurations, the Epic Link field is not shown or editable in certain screens or workflows (especially for company-managed projects).Fix for this: Go to the Screen Configuration for the issue type (Task). Ensure the field Epic Link (or Parent) is included…

Hi @Aleksandar Salevski From your log, I can see that <span>jira-servicedesk-application-5.12.15.jar</span>That version is from Jira 9.x — it’s not compatible with Jira 10.3.x, hence the “missing requirement / failed to load” message. Do this: Go to Administration → Manage apps. Locate the Jira Service Management…