Manoj Kumar Gangwar Community Champion

Hi @Luz del Alba García Fabián Welcome to the Community! You may try below: It converts your dates to midnight (00:00:00) before performing the diff calculation. {{customfield_10XX1.startOfDay().diff(customfield_10XX2.startOfDay()).businessDays}} If it does not work then try. Assuming an 8-hour workday, this converts total…

Hi @Ali Abdullah Welcome to the Community! You can achieve it via automation or workflow validators. If you don't want to modify the workflow, you can create an automation rule that reverts the status if a task is marked "Done" while its dependencies are incomplete. If you have Scripturnner or JMWE plugin, then you can add…

Hi @jessica.diem Welcome to the Community! Please use the rest api. https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-user-properties/#api-group-user-properties

Hi @Colleen Gotling Click on the + sign and then add a rule for the show screen.

Got it. So you have selected the groups in the manually trigger, those groups are not project groups. As per the current scanrio only user with the jira admin permission can see it and your colleague doesn't have the jira admin permission, he has only project admin permission. Just remove the groups from the trigger and…

Hi @Leo van Rijn could you please check the automation rule details and check what option is selected under "who can edit this rule?" 

Hi @Daniel Woodward Welcome to the Community! Please check the project permissions and then add yourself to the appropriate project role. Also, check if there is any issue security level applied for the issues. If it is a JSM project then you should have enabled the JSM Agent license and added it to the project role…

Hi @Christian Schulze Welcome to the Atlassian community. Have you confirmed that you are using the new billing experience that leverages the Billing Admin role? Based on the documentation only a current Billing Admin can modify the Billing Admins.…

Hi @Leo van Rijn Welcome to the Community! Only users with the project admin permissions can see the automation rules. Please the user permissions.

Hi @Stephanie Hambach Welcome to the community! Could you please share the error screenshot? Are you using the cloud version or the DC version?

Hi, @Sandra Bourgoin Welcome to the community! Could you please elaborate more on your issue or share some sample screenshots?

Hi @ariharan m Look at these posts, maybe they give you clues https://community.atlassian.com/t5/Jira-articles/Try-the-new-Jira-Cloud-add-on-for-Google-Sheets/ba-p/1016436 https://community.atlassian.com/t5/Jira-Software-questions/Automation-export-issue-fields-to-Google-Sheet/qaq-p/1520948

I already tied value {{webhookResponse.account.extended_profile.manager}} Here is the Rest API response: {"account":{"account_id":"712020:c005577b-dba6-4cb8-b712-d65b5d479c8e","name":"Aahanna Gowda","nickname":"Aahanna…

Hi @Simon Chauvin Welcome to the Atlassian Community! Team-managed projects use the "Story point estimate" field and Company-managed projects use the "Story Points" field.

You have to create the duplicate custom field for example orginial field is request type then duplicate should be request type 1. There is no way to use forms fields in the automation

Hi @Elsa Bronoel Welcome to the community! Currently, JSM forms do not support AND conditions. You need to create a duplicate field and use it. 

Hi @khawla You can edit the Priority scheme and change the default priority to None. To make the field mandatory, you can go to the project settings>fields configuration and search for the priority field then make it required.

Hi, @Kevin Robinson. It is only possible to change a table from full view to inline view, but then the images will become tiny. 

Hi @Küblböck Matthias Welcome to the Community! You had the admin access but it required JSM Agent license as well. Please grant yourself Jira Service Management - Agent license then add yourself to the appropriate project role, Service Desk Team.

Hi @Loic you can change the notification scheme or you can create an automation rule to notify. 

Hi @Rohit Sharma (Credit - GCM P&F)) Welcome to the Community! You can check with your colleagues or manager and ask them who owns the Confluence. 

Got it, so you can remove everything from ORDER By till the end then do the search and try to export.

Hi @Jira Users I found a workaround to fix it, after removing the ordered by fields(there was many fields added as order by ASC and DESC). You can check it when you change your query from Basic to Advanced.

Fixed it, after removing the ordered by fields(there was many fields added as order by ASC and DESC). You can check it when you change your query from Basic to Advanced.

Hi @Aron Gombas _Midori_ , @Denise Dobbins You can change your filter to query from Basic to JQL, remove the Ordered by fields, and try exporting it again. I did the same and it resolved my issue.

I'm getting the same error.

Hi @kamal.a.nayan you can set the resolution using the workflow post function instead of automation. Also, please share the automation audit logs screenshot to check the error. 

Hi @Grace Dowling you can raise a ticket with atlassian vendor using the below link for this issue. https://support.atlassian.com/

Hi @Janusz Mokrzycki Welcome to the community! Please refer to the below doc. https://support.atlassian.com/confluence-cloud/docs/bypass-access-restrictions-on-a-page-with-admin-key/

Hi @Benjamin Welcome to the community! Could you please share the screenshot of your board?