Trudy P Claspill Community Champion

Hello @Kerstin.Hares You can't add JQL to the trigger. You have to add a Condition component and use the JQL Condition. If you want the rule to proceed when the issue is added to an active or future sprint then the JQL you would use would be sprint in openSprints() or sprint in futureSprints()…

@David Nickell The poster indicated they are using Jira Cloud. In that product all parent/child relationships at all levels now use the Parent field. Atlassian made this change a year or so ago.Parent Link and Epic Link are deprecated.

Hello @Kavita Patil Welcome to the Atlassian community. Whenever you ask for help with an Automation Rule it will help us to help you if you provide: * screen images that show your entire rule, * screen images showing the details of the step(s) that aren't generating the result you expect * screen images showing the Audit…

Hello @Cindy Kim Can you provide a screen image showing the Validator configuration? Are there any other validators on that transition? Can you show an example image, showing the Parent field, where the transition failed? Is this for a Team Managed project or a Company Managed project?

Hello @Nonnie Ross Welcome to the Atlassian community. Hello yes I would like to know how to get my backups from jira so I can give more creation tips to the project Atlassian does not take backups of your instance to enable you to restore the instance. The backups they take are only for their own disaster recovery…

Hello @Niamh Russell Adding to this... If you are not part of the team/department that manages the Jira instance and billing then I strongly encourage you to contact those teams to ask for them to establish the Confluence Cloud subscription. Many company IT teams become very frustrated when employees strike out on their…

Atlassian support logged a bug about this: https://jira.atlassian.com/browse/AUTO-1592

Hello @Alexander Makarovsky As a debugging step you should print each of those smart values into the rule Audit Log so that you can see if the values being compared are what you expect. You can print information into the Audit Log using the Log action in the rule.

The status that indicates the work is complete and no additional work remains needs to be mapped to the column farthest to the right on your board. Jira is designed so that only the work in that right-most column is considered "complete" in the sprint. The red line will move downward only as issues are moved into the…

Hello @Christine Welcome to the Atlassian community. The Jira Automation Rules feature does not include a Move Issue action. When an issue is moved that process can require the user to make corrections such as selecting a valid status and issue type for the issue in the new project. Those sorts of interactive decisions…

Hello Heather, When you say the rule didn't work, it is helpful if you tell us exactly what it did and did not do. You don't need the Branch at all. You do need to use an If/Else block. When you use a series of IF conditions the rule stops running when if encounters the first IF condition that fails. With an IF/ELSE block…

if we want the Title of the Epic to change each time we clone it a Product Admin has to do that? No. What a Jira Product Admin can do is specify the prefix text that will appear automatically each time the Clone Issue feature is used. As an end user you have the opportunity to override that text when you execute the Clone…

Hello @akhilaa.susheela Welcome to the Atlassian community. The burndown does not occur each time you log work. The burndown only occurs when you move the issue to the last column of the board, indicating the work is done.

when I clone the Epic there is a section in the automation that will ask me for the new name of the Epic. When I fill in the name and select for the template to be cloned it does not change the name to the new name I entered and it adds the word CLONE to the Epic title. It also adds the word CLONE to the titles of the…

Hello @Joe van Teylingen Welcome to the Atlassian community. On premise storage of the data for a Jira Cloud product is not possible. If you are approaching the 2 GB storage limit you will need to either upgrade to a paid subscription or remove some of the items consuming the storage. Refer to this page for more…

Hello @Heather Hanselmann Welcome to the Atlassian community. Do I understand correctly that you already have a rule that is properly cloning all the issues? Can you please provide screen images that show the entire rule? What is your scenario for Statuses? Do your work items more from one status to another, or do they…

Hello @Hamza Ahmad Welcome to the Atlassian community. Have you explored native functionality to copy data from one cloud site to another?? https://support.atlassian.com/organization-administration/docs/copy-product-data/ There are many things to consider in the consolidation of multiple Jira Cloud instances into a single…

Hello @daniela zanini Please show the Audit Log for the rule where you executed it in the manner I recommended and there was no information in the log for Epic Link. Also show the version of the rule that was used during that execution. Are you setting the Epic Link when you create the issue using the Create button from…

Hello @daniela zanini Welcome to the Atlassian community. Branching to the Epic is the wrong strategy. When you use a branch you are shifting focus to the issues you identify in the branch. The actions within the branch are taken against that issue. So the way your rule is written, you are Editing the field in the Epic, by…

Hello @Narasimha Murthy Jalla Please note that the original post and my response are 3 years old Since then Atlassian has made many changes. Specific to this topic they started a transition from the use of the Epic Link field to using the "Parent" field in both Team Managed and Company Managed projects. They automatically…

Hello @Sam Hilsman Welcome to the Atlassian community. I have flagged your post here to raise it to the attention of Atlassian Team Members. You should see some sort of response from them within this post within 1-2 business days.

Hello @JerryD Welcome to the Atlassian community. What type of page are you referencing? Is it a page in a Confluence instance?

Hello @Vicki Tan Welcome to the Atlassian community. There are multiple products from Atlassian that include "Jira" in the name. Each is a separate product that you can subscribe to, but they can be integrated with each other for a more comprehensive feature set. Jira Jira Service Management Jira Product Discovery Jira…

If you have non-subtask issues in the right-most column that are moving to the next sprint, that is not proper functionality. It is a separate issue that should be investigated. Subtask issues in the right-most column will move to the next sprint if their parent issue is not also in that column because all subtask move…

Hello @blabla70 Jira does not natively provide a method for setting fields based on the email content when the email is processed to create the issue. You could use an Automation Rule, triggered by the completion of the issue creation, to parse the content in the Description field and set the two other fields.

Hello @Rodrigo Munizaga Welcome to the Atlassian community. Is the Jira subscription owned by a company? Is the email of the former Org Admin owned by the company? If so, the company can reactivate the email, assigning it a new password, and use that information to log in and add another user as an Organization Admin. Has…

Hello @Caroline Watanabe Welcome to the Atlassian community. What type of project are you using? Get that information from the View All Projects page under the Projects menu. How are you designating which squad owns the issue? Boards display issues based on a Filter. If you have a field in each issue that identifies the…

Hello @Veronika IVANOVA Welcome to the Atlassian community. What type of project are you using? Get that information from the View All Projects page under the Projects menu. Find your project in that list and tell us what it says in the Type column. The status must exist in the Workflow(s) used by the issues. To move an…

Hello @Sergey Shkut Do you have an existing rule that you want to modify? If so, please provide screen images showing the entire rule and the details of each step.

I had a mistake in my response that I have now corrected. Where I used "Impact" I should've used "Reach". The "get" function applies to the table, with the information in the parentheses indicating the key value. So the syntax would be {{tableReach.get(issue.Reach)}}