Manoj Kumar Gangwar Community Champion

Hi @ALLA ATCHYUT KARTHIK * Jira Admin Access: * Manage projects, issue types, workflows, and permissions within specific projects. * Configure project settings and create custom fields. * Manage users and groups for the projects you administer. * Organization Admin Access: * Manage all Jira projects across the…

Hi @Maghlazi Mariama Welcome to the community! You get this message when you exceed the tier of users for which you are paying - not the total capacity of the system. Check your billing to see what tier of user count you have paid for and increase that if necessary. You can remove license allocations from users by logging…

Hi @Nicolas Andika You can use. {{issue.parent.fields.components}}

Hi @Vivek J Please check your workflow, i think there is no direct transition from ready for prod to deployed in prod. If not then add the transition

This could be due to required fields are not added on the service request. Please use create button to test the required fields for that specific issue type which you are trying to create and then add those fields in the request. 

Hi @Akhil welcome to the community! Are you creating ticket from Slack or Teams? Please check the fields If required fields are not available then ticket will not be created. 

Hi @Martyna Majewska Welcome to the community! Please refer. https://support.atlassian.com/subscriptions-and-billing/docs/manage-payment-methods/

If it resolved your issue, please accept the answer to mark it as resolved. 

Please accept the answer so it marked as resolved. 

Hi @Victoria Luskin The status "In Progress" is enclosed in single quotes because it has a space. project = XXX AND status not in (Closed,Accepted) AND issueFunction in linkedIssuesOf("status in (fixed,accepted,closed)", "has epic") AND not issueFunction in linkedIssuesOf("status in (open, acknowledged, 'In Progress')",…

Please share the screenshot of IF block condition. 

Hi @Min Zhao Welcome to the community! Please refer below doc. https://docs.searchunify.com/Content/Content-Sources/Atlassian-Jira-Confluence-Authentication-Create-API-Token.htm#:~:text=You%20can%20copy%20the%20token,it%20in%20the%20password%20field.

Hi @Asheesh Welcome to the community! You can use the IF Else condition If count 1 then create 1 subtask Else count 2 then create 2 subtasks Else count 3 then create 3 subtasks

Hi @jay Summary field support only ~ and ! ~ operators. You can use summary ~ text1 OR summary ~ text2

I think empty fields are not hidden thats why they are showing in the tab and tab is not hiding due to this. If you have configured request type then under the request type click on issue view and move those fields under hide when field empty. Else you have to create the separate isaue types. 

Hi @Chris Thomas welcome to the community! If you know that the automation user is the one adding the comment, you can combine the comment search with filtering for the automation user who added it: status = Closed AND comment ~ "auto-closed" AND commentBy = automationuser() commentBy = automationuser(): Filters to…

Hi @Bhavik_Shah To resolve the issue of the case sensitivity for the assignee name in Jira, you can follow these steps: * User Management in Atlassian Admin: * Go to your Atlassian Admin Console. * Navigate to User management and then Users. * Search for the account "dev-platform-engineering". * Edit the Display Name: * In…

Hi @Rachel Frechette project = "YourProjectKey" AND updated >= startOfWeek() AND updated <= endOfWeek() Replace "YourProjectKey" with your actual project key. This query will return all issues that were updated during the current week.

Hi @Mike Puckett Welcome to the community! If you want to bulk update the summary field then you can find out all the sub-tasks using the JQL and export it to CSV including the Issue Key, and Summary fields. Update the summary on the CSV file and import it again At the time of mapping map the Issue Key and Summary It will…

Hi @Marta Perez Normally it is not feasible but as a workaround, you do this: You need to create three customfields and add one customfield on each tab apart from that you have to remove all other fields from the tabs. In the automation rule, you can set the field value based on the sub-task. For example- Sub-task1 then…

Hi @Harshit Grover As far as I understand, a post function is currently applied to the closed transition to set the Resolution fields. You can remove that post function and use it on the Resolved transition to set the Resolution field. On the Closed status, you can apply the below properties: jira.issue.editable: Set to…

Yes, you can skip. 

Hi @Adrien Riccardo Please check if the workflow has been published after adding the validator.

Hi @Selva Praveen Elango You can use the field required validator to make the Time Spent field required. 

Hi @Vivek J Welcome to the community! To create this Jira automation for deploying a Bitbucket change, follow these steps. You will need both Jira automation rules and potentially integrations with Bitbucket pipelines or APIs. Steps: Create a scheduled trigger: In Jira Automation, create a rule with the trigger "Scheduled"…

Hi @Michael Peterson Welcome to the community! Please refer to the below doc to create the custom roles in the project. https://support.atlassian.com/jira-service-management-cloud/docs/work-with-custom-roles/

So you can go under project setting>Forms Edit your form and you can drag and drop the attachment field position. If not then you can remove the attachment under request type and then add it the attachment field on the form. 

Hi @Anna Nguyen Welcome to the Atlassian community If the request type shares the same issue type you can simply change the request type on the issue. If the request type has a different issue type you will need to move the issue to change the request type.

Ensure that you're referencing the Time Saved custom field correctly. It’s best to verify the exact field name and ID (e.g., customfield_12345) by checking the field in Jira. This might look like: issue.fields["customfield_12345"]

It seems like you're almost there! You’re now correctly capturing the Fix Versions from the child issues, but the formatting of the {{childFixVersions}} value is causing the Epic’s Fix Versions field to be deleted instead of updated. The issue lies in how the values are being processed and fed into the Fix Versions field.…