Manoj Kumar Gangwar Community Champion

It sounds like the {{childFixVersions}} variable is capturing the child issue keys instead of the Fix Versions. This likely happened because lookupIssues by default returns the full set of issues, and if you're using the smart value incorrectly, it may be referencing the issue keys. To fix this and properly extract the Fix…

Hi @Yedan.Zhuang Welcome to the community! If your project members cannot find you in Confluence, and thus cannot grant you permission to view the workspace, here are a few troubleshooting steps you can take to resolve the issue: 1. Check Your Confluence License Ensure that you have a valid Confluence license assigned to…

Hi @Jane Nguyen As per my thoughts, it is not feasible. Let's wait for others reply. 

Hi @Amir Shmulevich Welcome to the community! To automatically update an Epic's Fix Versions based on its child issues' Fix Versions when the Epic transitions, you can set up a Jira Automation rule. Here's how you can achieve this: Steps to Set Up the Automation Rule: Go to Jira Automation: In Jira, navigate to Project…

Hi @Gregory Welcome to the community! Using the if/else structure is more efficient than stacking separate if blocks. You can achieve this with a single smart value expression using if/else like this {{#if(issue.fields.Time Saved <= 4)}}1 {{else if(issue.fields.Time Saved > 4 and issue.fields.Time Saved <= 8)}}2 {{else…

Yes, you can use that. 

Hi @Dee B , You can do the JQL search for both. For JSM portal, you can use the Request Type = 'request type name' For Jira create button, you can user the Issue type = Incident and request type is empty

Hi @Chasovskikh Kirill You can create the automation using the IF Else condition for the custom field value. Trigger> Issue Created Condition> Issue type = Bug Use If condition >Customfield-xxxx = xzy Then assignee = abx Else condition > customfield_1234= abc Then assignee = qwe and so on...

If you want to extract words or phrases after "Fiscalizador:", you can adjust the regular expression to allow letters, spaces, and possibly other characters. {{issue.description.match("Fiscalizador: ([\\w\\s]+)")}} \\w matches any word character (letters, digits, and underscores). \\s matches spaces (to handle multiple…

If you have site admin permission then you can access it.

Hi @Sarah Subrizi Welcome to the community! Login into 'admin.atlassian.com' > Directory > Invite user... On the User List, select . . . > Add user to group jira-admins-xxx, jira-software-users, and site-admins

Hi @Phap Hoang Welcome to the community! Currently, There are only limited fields you can show on the request view. Here is the list. 

Could you please test the smart values? {{issue.description.match("Fiscalizador: (\\d+)")}} OR {{issue.description.match("Fiscalizador: (\\d+)")[0]}} this one cleans up any special characters or formatting tags before inserting the value. {{issue.description.match("Fiscalizador: (\\d+)")[0].replace("{color}", "")}}

Hi @Marcelo Ignacio Cid Abud Assuming the text you need is in a custom field called Description, and you want to capture what follows "Fiscalizador:": {{issue.Description.split("Fiscalizador:").last.split(" ")[0]}} This splits the description text by "Fiscalizador:", then takes the last part of that split result and…

Hi @Dave Mathijs, It is not showing under project lists but the project description field is visible only to the project admins for Software & Service projects but not for JWM. Project settings > Details of a specific project.

Hi @Renuka Paladugu , Currently, the description for the JWM projects is unavailable. It's available for Software projects or Service projects.

Typically, the issue assignee is the person who moves the issue to Resolved. Here is one possible solution that you try in your automation rule using the smart value {{initiator}}. or you can select "User who triggered the event" Here is the link on smart value for user object for your reference…

Hi @Swapnil Welcome to the Community! you can copy the reporter value from the trigger issue to the assignee field.

Hi @Osama Al-Areky , Confluence offers some degree of integration with Jira, direct task transitions and detailed management are best handled within Jira itself.

Hi @Juan Vicente Rodriguez Rodriguez Welcome to the Community! Please refer to the below thread- https://community.atlassian.com/t5/Jira-questions/Some-issue-types-are-unavailable-due-to-incompatible-field/qaq-p/326167

Hi @Dd You may try [ {{#issue.components}}{{name}}{{^last}}, {{/}}{{/}} ]

Hi @Lara Lopez Garcia I think It is not feasible. The actual updated field doesn't care how the update came to the issue but just reflects that there was an update.

Hi @Usharvi Naik , It means you don't have sufficient permission on the particular project so ask the project admins to check your authorization and grant you the right access.

Hi @Sana Usman , Welcome to the Atlassian Community! You can check the automation rule audit logs or you can share the screenshot of the automation rule along with the audit logs to check this issue.

Hi @Hima Hebbare Welcome to the Atlassian Community! Could you please check if there are any page-level restrictions applied on your page or any restrictions inherited from the Parent page?

@Angela Wagner If our responses were helpful please consider clicking on the Accept Answer buttons to mark your Question as Solved.

Hi @Apryl Harris , You can vote on the suggestion below as this feature is unavailable in Jira Cloud. https://jira.atlassian.com/browse/JRACLOUD-64995

Hi @Khuram Khalil Jira recognizes that an email relates to an existing issue when the Subject of the email includes the Jira Issue Key. Have you tried adding the Issue Key for the created issue into the email subject of your first reply? If the issue key is in the subject line then check the "Add Comments" permission for…

Hi @Stefano De Santis You can create an automation like below example: Example of Automation Rule Configuration: * Trigger: Issue Transitioned * Status: Canceled * Condition: Issue Fields Condition * Field: Issue Type * Condition: equals * Value: Initiative * Action: Branch rule / related issues * Branch: Children * Action…

If its already created then you can proceed with next steps. Or if you have JMWE plugin then you can copy the group users to request participants field using the workflow post function.