Bill Sheboy Expert

Hi @Akeem Ibrahim It is likely this is possible using the math expressions for rules: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ Some things to note for such a rule: * consider what to do when any of the fields needed are empty * consider under what conditions you want the…

Hi @jaison dsouza First thing, it appears you have duplicated this question with another post: https://community.atlassian.com/t5/Jira-Software-questions/How-to-get-the-users-list-by-automation/qaq-p/2318264 Please consider closing out one of them. Next, what problem are you trying to solve by doing this? Knowing that may…

Hi @Calvin Smith Do you mean a pre-filled in template, or something after an issue is created? Automation rules run after an event, like issue create. And so the format would not apply before. When you need a template I suggest looking into an addon for templates, or another mechanism to guide input, such as a form in…

Hi @Tracy A Stimac You noted: Is it possible to reset estimation/velocity when there is a major team change? How would you envision that working? Jira tracking of velocity is based on what happened for a specific Scrum board for specific sprints. That is historical data. Changing the history would not necessarily reflect…

Hi @Eric Spiegel Yes, and...I agree with Dave: pick the first one and just do it :^) If you really, really...want the item to be a surprise/random one, you could probably write a rule using the Lookup Issues action, the random() and other math functions, select an item with get(), and then start it. Doing this, you would…

Hi @Holly Robillard -- Welcome to the Atlassian Community! When you note that none of the things you tried worked, what did you observe happening? Would you please post an image of the audit log details showing the rule execution? That may provide some context for this symptom. Thanks! UPDATE: I tried this and this worked…

I am glad to learn that helped. In that link I provided, documentation walks through the specifics for updating fields with JSON. The technique you use depends on if you want to replace or add to the existing values. Let's assume you want to replace the values in the Subtasks with those from the Story. The simplest syntax…

Hi @Niklas Malmberg First thing, there is a copy for fields like Fix Version...it is just a bit tricky to find it. This can be done without the advanced edit JSON when you want to replace the value. * add your Issue Edit action * select your Fix Version field * select Copy at the right side under the ... * then select the…

Hi @Serena Romeo -- Welcome to the Atlassian Community! You could try using the field change smart value which seems made to do this: {{addedfieldChange.values}} Please look here for more information: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange-- Kind regards, Bill

Hi @Richard Muffler Yes, and...to Mikael's answer: This is fairly easy for just the issue create scenario. However if you want to do more between JPD and the other projects after the issues have been created, you would probably need a global or multi-project scope rule to access the issues. There are limits on the number…

I am glad to learn that worked! Regarding your question about the first split on underscores... The first split on underscore created a list (not an array), and when that was then put into the created variable, it was automagically joined back into a text string separated by commas. Effectively it did this:…

That appears to be the cause: a created variable is text, not an object or list. Please try splitting the variable in the advanced branch source with: {{myList.split(",")}}

Are you using Jira Cloud or Server/Data Center? If you are using Server/Data Center, automation does not support Lookup Issues. Instead the bulk-handling option is available for the scheduled trigger or for branches: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html

Hi @Kunal Kumar Please look at the documentation for this feature to learn how to use it: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--lookupIssues-- Kind regards, Bill

Hi @Adam Ziecik I do not believe so, as this approach uses the Lookup Issues action, which is not supported by the Server/Data Center version you are using. Please see the other thread for my additional suggestion. Kind regards, Bill

Hi @Kunal Kumar In general, it is a good idea to create a new question and link to older ones. Otherwise only the people following the old threads will see them. Next thing, please post images of your complete automation rule, showing the details of the lookup issues definition, and of the audit log details showing the…

Let's try creating a new rule, avoiding any possible things broken under the hood for this one. After creating the rule, let's see what happens. Rules can get glitched if they are edited too many times...I have no idea why. * trigger: issue transitioned to Released, Removed, Fixed, or Done * branch: to parent epic* action:…

Please post an image of the advanced branch action for myEntry. Thanks!

Yes, I understand what you are saying: you expected to see this three times: "current myEntry is ..." For some design reason, the implementation of branches is "smart" in that it collapses these down in the audit log because the prefix is the same, even though the loop does process three times. I personally consider this…

Hi @Kunal Kumar -- Welcome to the Atlassian Community! First thing, using automation rules requires both learning and experimentation. I encourage doing both to see what can help to solve your needs, and when you get stuck to then post a question to the community. To get you started on creating your rule, please review…

The -2 days I noted was to subtract the first and second days in the entire range, and was unrelated to weekends. The use of businessDays in the diff takes care of the weekends.

A key question is: do the weekly issues finish during each week? If so, you can probably use a JQL statement to find the issues, iterate over them with either a scheduled trigger or branch on JQL, and create (or clone) to new issues. If they do not finish during each week, you will need a way to create the set of issues,…

Thanks for the images of your rule, and the action setups for the variables. Based on what you show, the audit log does show each value is getting processed. If the advanced branch still matches your earlier images, this seems correct. What is not working as you expected?

Mary, I think I missed something from the beginning of your scenario...I thought you were adding a single weekly issue, for each week. Do you instead want to add several different issues, which re-occur for each week?

Hi @Tory Dennis -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? How would the team(s) behave differently if you had that information right now? Knowing these things may help provide some context so the community can offer suggestions. Thanks! Kind regards, Bill

Okay...that is curious. If you can find a way to post the entire rule and audit log details images, that may help explain it.

Progress! Okay, for the assignee you can use the same technique with lookup issues, if you want the same person assigned: {{lookupIssues.first.assignee.accountId}} If instead you want someone specific, or to use round-robin, etc., you can do this: * ...some rule steps * action: create issue * branch: to most recently…

When you have a list, you can access a specific item by: first, last, an index with get(index), or by match() with a regular expression. If you instead need all of them, try the split() to feed the advanced branch.

Can you show me just your advanced branch setup and the smart value (or created variable) that feeds that? With those we can probably get the branch working fairly quickly, as the split may just be in the wrong place.

When you are trying to post an image of a longer rule, I suggest selecting the trigger in the rule editor, and then using a scrolling page capture tool. That will show the entire rule in one image. Would you please post an image of the advanced branch? Again, I suspect the problem is the source smart value is not split,…