Gor Greyan Expert

Hi @Dick Thanks for the reply. The interesting part of your audit log is that the lookup itself works correctly, while the Domain expression is already empty before distinct really becomes relevant. I would therefore go one level simpler and inspect how Automation for DC is exposing this particular multi-select field.…

Hi @Chathuranga Perera Happy, that the issue is resolved. If one of these answers helped you, kindly ask you to accept it. Regards, Gor

Hi @Chathuranga Perera Could you share the exact error message or a screenshot of what you see when opening? Community members don't have access to your instance; we can't check anything on it. You can also ask your site administrator to check your permissions. Regards, Gor

Hi @Dick I think the issue is with the structure returned by the multi-select field, not the lookup itself. lookupissues gives you a list of work items, and each work item has its own list of Domain options. So effectively you have a list of lists. You need to flatten that collection first and then apply distinct. I would…

Hi @Ian Court Welcome to the Atlassian Community! It's possible. In Goals, the feature you're looking for is called a saved view. Go to the Goals directory, apply the search and filters you need, then select Create view in the top-right and give the view a name. The view saves those filtering criteria, so you can return to…

Hi @Benjamin Zhou Happy to help you!

Hi @Sunny Tsai Welcome to the Atlassian Community! Settings --> Work items --> Field schemes --> select your scheme Find the field and choose More actions --> Change field behavior by work type. From there, you can use Replace field descriptions on work types to provide a different description for that field for a…

@Priyadarshini R No, Microsoft Graph specifically is not mandatory. But Python itself isn't a mail server, so it still needs an email service/provider to deliver the message. Jira REST API → run your JQL → calculate the SLA percentage → build the report → send the email For the last step, you could use your organization's…

Hi @Apoorv Sahai Welcome to the Atlassian Community! The 5,000 ideas per JPD space is a product limit, so if you already know your migration will exceed that number, I wouldn’t recommend designing the solution around a single space. The better approach is to split the ideas into multiple JPD spaces based on a meaningful…

Hi @Priyadarshini R Welcome to the Atlassian Community! One thing to clarify: where is the SLA data for your custom report coming from? If you're using native JSM SLAs, an SLA Marketplace app, or calculating the SLA yourself, the API/data retrieval part will be different. You can query the required Jira issues using the…

Dear @Troth_ Stefanie Great! Also, if the solution help you, kindly ask you to accept the answer, as other community members see it as resolved :) Have a nice day!

@Troth_ Stefanie In that case, unfortunately, Jira Cloud Automation doesn't provide a native preview of future executions/results before the rule actually runs. For testing, I would temporarily clone the rule, replace the Scheduled trigger with a Manual trigger, and use Log actions to output the calculated dates instead of…

Hi @sharyn keegan Welcome to the Atlassian Community! Being a Jira admin doesn’t automatically guarantee access to every board. I’d first check whether the board’s saved filter or its sharing permissions were changed, as the board can remain visible in the list but become inaccessible. Can you share the exact permission…

@Troth_ Stefanie For the Crone Expression, it doesn't provide Upcoming Execution, but for the Basic one, it is available. If you need Crone, for Every Monday at 09:00, you can use this. 0 0 9 ? * MON *

Hi @Sara Salem Glad that you could find a solution. Please also accept the answers that were helpful to you so other community members can find a solution. Regards, Gor

Hi @Troth_ Stefanie Welcome to the Atlassian Community! You can achieve this with one automation rule, but not by adding two separate CRON expressions to the same Scheduled trigger. As you need the work item created at 08:00 on the second Monday and the last Monday of every month, I would configure the rule to run every…

Hi @Benjamin Zhou Welcome to the Atlassian Community! Go back to the project's Work item layout configuration. You should see the fields that are not currently placed on the layout in the Fields section on the right side. Find the field you removed and drag it back into Hidden when empty fields, then save the layout.…

Hi @Jaegap Welcome to the Atlassian Community! To change this name, you'll need to contact Atlassian support. A similar request is this one. https://community.atlassian.com/forums/Goals-and-Projects-discussions/Renaming-Workspace/td-p/2312681#M143 @Andrew Hammond could you please assist with this?

Hi @David Gutierrez Happy to help! Have a nice day.

Hi @David Gutierrez Welcome to the Atlassian Community! Yes, Jira Align is definitely still worth learning. What has changed is mainly how Atlassian positions it. Rather than looking at Jira Align completely on its own, I would look at it as part of the broader Strategy Collection, together with Focus and Talent. In simple…

Hey @Davy Jacops Thanks for the reply. In JSM an Internal note is not a separate field. It is a comment with internal visibility, as opposed to a customer-visible reply. Since your Rovo agent itself is performing the Jira update, I would first check the Tools configured for the agent in Rovo Studio. The important question…

Hi @Davy Jacops Welcome to the Atlassian Community! Could you clarify how the Rovo agent is currently posting the response back to the Jira ticket? Are you using a Jira Automation rule with Use Rovo agent followed by an Add comment action, or is the Rovo agent itself configured with a Jira tool/action that posts the…

Hi @Eric Pujo Welcome to the Atlassian Community If you want the Excel column to become an actual Jira Checkbox custom field, Jira Cloud's CSV importer supports mapping CSV data to an existing Checkbox field. https://support.atlassian.com/jira-software-cloud/docs/mapping-csv-data-to-jira-fields If you mean interactive…

Hey @유지혜 Thanks for the clarification. In that case, you do not need to migrate the Jira data to a new site. You can keep the existing Jira Cloud site and update the organization/company details and the users' Atlassian account email addresses to the new domain. Your existing Jira work items, comments, history,…

Hi @007989 Welcome to the Atlassian Community! Your smart value is correct That behavior is more likely caused by timing/indexing. The rule is triggered immediately after a child Story Points value changes, while the updated work item may not yet be available to the JQL used by Lookup work items. I would try adding…

Hi @유지혜 Welcome to the Atlassian Community! I would first confirm whether you need a new Jira site/Atlassian organization, or whether this is simply a company name and email domain change?

Hi @Javier Martínez Welcome to the Atlassian Community! Jira's native JQL can filter the work items, but it cannot calculate a SUM. Your JQL would simply be -- sprint = 1234 AND component = FE If you only need to see the total Story Points for that sprint/component, one simple native option is to save this filter and use…

Hi @nboreddy Welcome to the Atlassian Community! This isn't possible with Jira Automation. Entering a value there only filters which work items are displayed on the board. It does not change the work item or fire a Jira event, so no Automation trigger can detect that a user searched for Test. Automation rules need an…

Hi @Guram Welcome to the Atlassian Community! The login count is cumulative, so it cannot be filtered to calculate how many times a user logged in during only the last three months. Jira can provide the last login date, which lets you identify users who logged in during that period, but not the number of individual logins.…

Hi @Adam Hudson Welcome to the Atlassian Community! You're not missing a configuration option here. Jira Plans currently doesn't support the traditional dependency types Start-to-Start, Finish-to-Finish, or Start-to-Finish. Dependencies in Plans are essentially treated as Finish-to-Start: work item A blocks work item B, so…