Bill Sheboy Expert

Hi @Jai Ganwani Yes, and...to Nic's answer: When the sprint completes and the team sees the goal was not met, or more / less than expected was completed, that is great information for the team to take into the retrospective. They can ponder "why" and select experiments to improve in the future, such as adjustments to…

Please post images of your complete automation rule, including the details of your Clone Issue action, and of the audit log details showing the rule execution. Those may provide context for what you are describing.

Hi Artur Balyan @ Immedis First, some tips... When posting an automation question for a longer rule, please try using a screen capture or browser addon so the entire rule is in one image. That will help ensure the context is shown relative to the audit log. (Posting multiple images makes it more difficult to follow.) Next,…

Hi @Jignesh Jaiswal When you use the Clone Issue action in an automation rule, you have the option to override the value of any fields. So if you do not want a field to copy from the source issue, just select that field in the action and clear the value. If the field is not shown in the drop-down list, you may use the…

Hi @Andrew Morse Thanks for helping answer the community questions about these changes. Based on your response that the Re-fetch Issue Action counts for the limits, I have a couple of suggestions: #1 Please update the automation documentation to indicate which actions count toward the limits. This could be similar to the…

Hi @Aron Gombas _Midori_ When I have tried that method in the past (for lookup issues and web response) the results were stored in the created variable as text, requiring more complicated parsing...and no smart value names unless the results were stored as JSON. Please see my post for using lookup tables for another…

Hi @Shir Avtabi -- Welcome to the Atlassian Community! It is not possible to have multiple, active Lookup Issues results in a rule at this time. A work-around is to use the new Lookup Table issue to store the results; the "value" field of a table is an object and may be referenced the same as the lookup. For example... *…

Hi @Thao Do -- Welcome to the Atlassian Community! Here is an automation rule I wrote to calculate Age of WIP a few years ago: https://community.atlassian.com/t5/Automation-discussions/What-is-your-most-useful-automation-Here-is-mine/m-p/1561072#M34 This one calculates in calendar days, and can be modified to do so in…

Hi @Ralph I do not believe that exists yet. There isn't even a public REST API for rules yet to fill that gap. Perhaps create a suggestion for this idea here: https://jira.atlassian.com/secure/Dashboard.jspa Kind regards, Bill

Awesome; I am glad to learn it is working! Please consider marking this question as "answered"; that will help others with similar needs find solutions faster. Thanks!

Thanks for the additional details. It appears the board has some "policies", like the WIP limits you are using, and that because multiple people can move things the limits are not being followed. That seems worthy of a discussion to learn why: is it a training issue, an unknown problem, etc. The rule I suggested will move…

Hi @Heather Marquez I'm following up based on the ping from Trudy. (hi, Trudy!) Apologies in advance for the long answer... First thing, the scenarios you describe seem better supported with tools like Jira Service Management (JSM), rather than trying to re-implement some of those features with Jira. You may want to…

Hi @Andrea Smart First a few questions to help focus your approach... How are issues moved from the "defects" to the "priority" column? Is it with another rule or manually? And if manually, why is the team pulling over more work when their capacity is full? How do you know if your team is / is not working on something in…

You appear to have 2 Lookup Issues actions, and you do not need the second one. The first lookup will find all of the issues linked to your epic. And then in the edit you just use the expression I suggested: {{lookupIssues.Start date.min}} That will find the earliest Start Date within the looked up issues.

Would you please also post the audit log for the rule, expanding the details for any time the rule was triggered? That will help to compare that information to what you show in the issue history.

Hi @koutarou ishibashi Context is important for automation rules; would you please post images of: * your complete automation rule, * including where you have that smart value expression, and * of the audit log details showing the complete rule execution, with that error? Those may explain the symptom you are observing.…

Would you please post an image showing that, where the story CON-375 has child Tasks? The out-of-the-box issue type hierarchy for Jira Cloud is: * Epic* Issue (e.g., Story, Task, Bug)* Sub-task Task and Story are at the same level, and so one is not a child of another. I suspect that instead your issues are related as…

I am using Jira Cloud, I repeated your exact rule write to the comment and it worked for me...again. Rules can get "glitched" with too many edits; I have no idea why this is, and... We can check if that is the cause by trying this: * Disable your rule, re-enable it, and test again. If that does not help... * Disable your…

Well done! That was the second approach I was describing. As you want to synch (not incrementally add / remove) labels, this should work. And as this is going from the Labels field as a source, I do not believe you need handling for special characters.

Hi @Graeme Baker First thing, are you using Jira Cloud? If so I recommend reading this article announcing a change to the packaging / licensing model for automation rules. Unless you are on the Premium or Enterprise level license I suspect the rules you describe will be impacted and have cost implications for synching the…

Hi @jeoj First thing: what problem are you trying to solve by doing this? That is, "why do this"? Knowing that will help the community to offer better suggestions. Until we know that... A web request in a rule can only send issue data when there are issues. You do not show your automation rule to confirm, and I wonder if…

Hi @Harrison Magee -- Welcome to the Atlassian Community! I have not used Jira Product Discovery (JPD) with delivery teams in that way, nor have I learned of others doing so. Although a "team" field could be added to a JPD project, it would have no meaning to the rest of Jira...unless someone manually linked to Jira…

Hi @Jon Green Looking at the image you posted, are you stating that user story CON-375 has subtasks? If so, those should display. If they are instead linked to other issues, those will not display. This view in Jira Product Discovery apparently only recognizes issue configured in the hierarchy and not issue links. Kind…

Hi @Judefrank Mercy -- Welcome to the Atlassian Community! Yes, you can do that with Jira, and I encourage you to discuss this situation with your team and their scrum master / agile coach, such as during a retrospective. The way you have described your question leads me to wonder if you have "developers", "testers", etc.…

Awesome; I am glad to learn it is working now! What did it: the disable/enable, re-create the rule, something else?

Hi @James I recall it is not possible for customers to change those defaults. (Which is a serious problem since the addition of Jira Product Discovery...) At my last company, we contacted Atlassian Support and they were able to change the defaults for us. If you are on a paid Jira license level, your site admin can submit…

You describe cloning an existing issue, and so a simple rule to do that would be: * trigger: sprint created * branch: on JQL to the issue you want to clone* action: clone issue, copying the fields as needed You also note the issue has many checklists. If you are using a marketplace app for checklists, please look at that…

Please look here to learn about creating/saving a filter: https://support.atlassian.com/jira-software-cloud/docs/save-your-search-as-a-filter/ Please look here to learn more about the syntax of JQL filters: https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/ And if you…

I will try to answer the different questions you asked there...Please let me know if I miss any of them :^) A scheduled trigger rule runs on its schedule. It cannot have a dynamic schedule based on issue data. This trigger can use JQL to gather issues on that schedule, helping to manage executions. (For example, create a…

Awesome; I am glad to learn that helped!