Bill Sheboy Expert

Hi @Anastasiia Tsvetkova To try to help with your scenario, would you please answer these questions: 1) How many versions does your team have unreleased when this rule is running: just one for the next release, or future ones also? 2) Does anyone on the team ever manually release a version? 3) Are there any other rules…

Awesome; I am glad to learn that helped you.

Hi @Shreyas Kogalur -- Welcome to the Atlassian Community! Adding to Walter's answer... What features are you looking for in "plans"? There is already a basic, timeline feature available for project boards: https://support.atlassian.com/jira-software-cloud/docs/roll-up-dates-on-your-timeline/ And if you are looking for…

Those images seem to indicate the rule worked: the component values from TP-131 were copied to TP-180. What is not working as you expected?

The only tricky part about a rule like this is setting the issue links: when you type in the smart value, it appears below the field, and then it can be selected for use to link the issues. Here's an example rule. The links must be added one at a time, due to limitations in the rule actions (and supporting REST API…

Hi @Joe Tobey There are a couple of solutions for that... First, as issues are created in the main execution path of the rule, two smart values are available: {{createdIssue}} and {{createdIssues}} (note the plural). With the second one any of the previously created issues could be referenced using the get() function in…

Let's stick with Trudy's thread as she has the correct cause. Thanks!

As Trudy described, because the project you are cloning to is a team-managed project (TMP), it will definitely have a different Issue Type (and id), even for the same named task. This is a known problem, as described here: https://jira.atlassian.com/browse/AUTO-410 A possible work-around would be to create the issue using…

Please post images showing the component fields for the issues TP-131 (the source for the components) and TP-180 (the issue you are copying them to). The rule seems to indicate the copy worked. And, please post an image of the edit issue action for the rule. About that message and the issue showing up: you may want to…

Hi @Tempo Digital -- Welcome to the Atlassian Community! That error may mean a couple of possible things: * Because your clone action is using the option "Same issue type as trigger" the source issue type does not exist in the other project. To solve this, I recommend selecting the specific issue type in that action. * The…

Hi @Brandon Fritcher -- Welcome to the Atlassian Community! You could do this with an Advanced Branch, iterating over the users selected in your custom field: https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935 To prevent timing problems in the rule, I suggest…

Hi @Gregory BENARD Automation rule logic uses the information in the trigger issue(s) from the time of the rule start. When you update a trigger issue in the rule and want to use that update later, please add a Re-fetch Issue action after the edit. This will reload the data before proceeding.…

Hi @snwatts6 -- Welcome to the Atlassian Community! Adding to Jack's answer: Here is the documentation on more advanced JQL searches, including a link to the list of functions (at the right side of the page): https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-search-in-jira-cloud/ Kind regards, Bill

Hi @Ray Stark -- Welcome to the Atlassian Community! In your rule image, the Feature issue create is trying to set the "Epic Link" to {{epickey}} and the branch is trying to create the child issues and link them to the just-created Feature, using the smart value {{feature.key}} Neither of those smart values exist. Before…

Awesome; I am glad to learn that helped!

I am glad you found a work-around, and... Are you using Jira Cloud? If so, I just checked again and a smart value can be typed in for linking issues, both for the Create Issue and the Edit Issue actions. Earlier I noted the steps how to do that. If instead you are using Jira Server, I do not know if that method works.

In that case, the edit cannot be inside of the branch as it will edit the linked issue. And so your rule will need another approach to find the latest due date... For your Jira version, do you have the Lookup Issues action?

Smart values are case-sensitive. Please try using what I suggested above for the link key: {{triggerIssue.parent.key}}

You are using the Lookup Issues action with what appears to be the same JQL twice. Is that correct, or is it just not showing all of the JQL in the rule image? Each could match what you are trying to do: all story points: "Epic Link" = {{triggerIssue.parent.key}} completed story points: "Epic Link" =…

Automation rules do not display such messages after they edit issue fields. That message would only show if you manually create or edit an issue, setting the fields in a way that it no longer matches your board filter. That seems like an unrelated problem. Back to your automation rule, what do you observe happening when it…

At the right side of that view, above the displayed issues, there is a Columns drop-down list to select which fields are displayed for the search.

Hi @Anush Chatikyan As this is an older thread, I recommend creating a new question and linking back to this one. Otherwise that limits the suggestions to only those people following this one. Thanks! Until then... Please see the above post, as how the issue is cloned determines how to change the status. Kind regards, Bill

I just noticed an error in your increment, smart value expression...When you increment the value, the branch is already to the parent. And so the smart value should be: {{#increment}}{{issue.properties.Operation_ID}}{{/}} or more simply: {{issue.properties.Operation_ID.asNumber.plus(1)}}

Please try writing JQL to return the issues that you want to sum up, or the Epics which have child issues you want to sum. Test that JQL outside of a rule, using View All Issues from the Jira menu. That JQL may then be used with a scheduled trigger, processing up to 100 epics at a time until they are all caught up. Then…

As a suggestion, when responding please try to stay with the same thread. That will help others in the future know if there are multiple solution approaches for a question. For the image you show, I notice your rule is triggered on a change to the sprint field. This will happen any time the value changes. My question is,…

Hi @Alex -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for…

Adding on to the JQL you already have, please try: AND "Master Priority" >= {{triggerIssue.Master Priority}} But before you do that, please check a couple of things... Confirm that field name in JQL, perhaps with a test query outside of the rule in View All Issues. Next, smart values are name, spacing, and case-sensitive.…

First, please check your personal settings to see if you have notifications enabled. Next, who made the change to the subtask? If you did it, I would not expect you to get notified (as you did it). Please ask someone else to update an issue you are watching to observe what happens.

Please post an image of your current, entire rule. That will provide context to help decide where to add the manage watcher action.

Hi @Jason Mills -- Welcome to the Atlassian Community! I have seen posts from others suggesting that, for example this one: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Timeline-view-feedback/qaq-p/2245417 I recommend looking in this specific area for the JPD information to learn more as they improve…