Gor Greyan Expert

Dear @psubhas1 Glad that the issue is solved. If the steps provided above helped, please accept the answer.

Hey @psubhas1 HERO029420 is the project name? Are you a Jira Admin for your site or not?

Dear @Arkadiusz Wroblewski I didn't say, that automation can't do that, but @Carles Mata mentioned that they ran out the automation limit, so the automation itself should not be the reason for this case. Surely, wrong automation logic can be the reason for this case.

Hi @psubhas1 I’d suggest the following steps: * Try opening Jira in an incognito/private window * Clear browser cache and cookies * Try a different browser or network * Confirm you’re logged in with the correct account and have access to the site If the issue persists, ask your Jira admin to check site status and user…

Hi @Carles Mata Did you check other automation tools, like ScriptRunner(Listeners) or External Integrations (e.g., Exalate, API syncs, apps)? These can overwrite the Labels field right after you edit it.

Hi @zhangxue Welcome to the Atlassian Community! The error message “Something went wrong on our side” indicates that the failure is occurring during Atlassian’s site provisioning process. The most likely causes are 1. Site name already reserved. Even if the URL looks available, Atlassian site names must be globally unique,…

Hi @류형근(모빌리티인포테인먼트개발TF) Welcome to the Atlassian Community! Could you please provide a screenshot of what happens when you try to log in? I’d recommend checking: * Whether the user (***@kt.com) has been invited to ktdevspace.atlassian.net * If they have an active Jira product license assigned * Site access under…

My First ACE - Mastering Jira Automation, Workflows & Extending with ScriptRunner was in Yerevan, organized by @Anahit Sukiasyan Anahit jan, thanks for the great event :) 

Hi @Crystal Miller Thanks for the question. This usually isn’t expected behavior, as attachment previews in Jira should load consistently. When previews fail to load and then appear after a refresh, it’s often related to caching, browser behavior, or network conditions rather than the attachments themselves. A few things…

Hi @Ramesh Krishnan Thanks for the question. Go to Settings --> User management (or Directory, depending on your Jira version) Open the Groups section Click Create group Enter a Group name Click Create Also, check the documentation. https://support.atlassian.com/user-management/docs/create-groups/

Dear @Marigona Alimi Try clearing the browser cache anyway. If not, you can create a ticket or wait to be fixed :D

Hi @Marigona Alimi Also, I am receiving an error like "An unknown error occurred". I checked the status page, but there is no active incident now, or they haven't reported yet :D https://rovo.status.atlassian.com/

Hi @Pam Brechlin Welcome to the Atlassian Community! Also, I am receiving an error like "An unknown error occurred". I checked the status page, but there is no active incident now, or they haven't reported yet :D https://rovo.status.atlassian.com/

Dear @Marc -Devoteam- Thanks for the information, will try to figure out.

Hello @keerthika Narra Thanks for the question. The Component field does not behave like Labels. Users cannot freely create new components unless they have the proper project permission. If the user can create new component values directly from the issue edit screen, it means they have the Administer Project permission.…

@Marc -Devoteam- Thanks for the information. But one thing to validate, the Create button should be available under the active sprint, is it a fact?

Hi @Noelle Bareswilt The Microsoft Teams integration creates issues via the Jira Cloud REST API. Jira enforces required fields at the field configuration level through API validation. The Teams create dialog is a simplified integration UI and does not dynamically inherit project screen schemes. Therefore, if a field is…

Hi @Marc -Devoteam- Thanks for the information, but I am a Jira Admin and have all the permissions for that project. Also, that colleague has that permission. Also, this "issue" has appeared in all projects

Hi @John Phillips Welcome to the Atlassian Community. The Sprint Burndown Chart is sprint-based and tied to a Scrum board sprint. It cannot be configured to run from a saved filter, release, or issue set outside of the sprint context. It helps to monitor whether they are on track to complete sprint commitments. You can…

Hello @Pfdev11,@Bill Sheboy Yes, Bill, you are right, it inherits the sprint value from the parent, but you can find that tickets using JQL and searching, that sprint is that sprint and issuetype is sub-task, for example. I am sharing my automation's audit log, where it is visible that action was done and tickets was…

Hi @Brian Nørvig Thanks for the question. Did you check if that agent has Jira Service Management Agent product access?

Dear @Tomislav Blažinović If this was useful for you, kindly ask you to accept the answer.

Hi @Tomislav Blažinović Welcome to the Atlassian Community! In this article, it is described how to reactivate the subscription. https://support.atlassian.com/subscriptions-and-billing/docs/reactivate-a-subscription/ If you're having issues reactivating, you can contact Support https://support.atlassian.com/contact/#/

Hi @Pfdev11 Thanks for the question. I tested this logic, and it works. Please also check on your side. Trigger: Sprint Started Branch Rule: For JQL, put this JQL sprint = {{sprint.id}} AND issuetype in subTaskIssueTypes() AND assignee IS EMPTY AND summary ~ "Testing|Unit" Condition: Parent Issue --> Assignee is not empty…

Dears, I get this one, which retrieves my needed date. It was impossible to set it in the summary, as it exceeded the 256-symbol limit, but I did it via a custom field, then copied it to the summary. {{#if(now.format("e").equals("1"))}}{{now.plusDays(1).format("yyyy-MM-dd")}}{{/}}…

@Danno It is an automation rule. It is being opened by automation, but in summary, there is a need to write the day of the next Monday.

Hi @Aron Gombas _Midori_ Tried this one, but it returned an empty value. I tested it in the log action before the summary change.

Hi @J B This isn’t working because Jira treats a default value as if the user already entered something themselves. From Jira’s point of view, the field is no longer empty, so the “required” rule is skipped. Because Jira validates fields purely on a technical level, it has no way to tell whether the user meaningfully added…

Hi @Simone Edmondson If you know who your Jira Admin is, you can contact them to check the access; if not, you can contact Atlassian Support. https://support.atlassian.com/contact/#/

Hi @Michael Green Did you change the " yourdomain part to your domain? If yes, please also provide a screenshot. I will help figure it out.