Bill Sheboy Expert

When looking at a workflow, you may select one of the lines connecting the status values you are interested in updating. That should show if there is a rule on the workflow, which you may then edit or delete. I believe for classic projects you will need to publish the workflow after that. Please look here for more details…

Hi @Rick Hoyle Have you tried using the updatedBy() function? For a specific user, this can show you issues they changed, and optionally within a time range. Please look here for details of how to use the function:…

That is interesting, and I am not familiar with that default setting for a project. What type of project is it: team-managed (next-gen) or company-managed (classic)? Would you please check to see if you have any automation rules set up? You may find them from the board by selecting the lightning bolt icon > manage…

Hi @Rafael Thomaz If a user is automatically assigned when an issue transitions to a new status, something is doing that; it is probably an automation rule or workflow action. Please check for use of those and remove the one(s) you want, or change them to clear the assignee instead. Best regards, Bill

Hi @Kelley Mills I note that you said you can't show screen shots, but posting an image of your rule and the audit log from execution will help the community offer ideas. Consider if there is a way to obscure what you do not want to show in the images before posting. Without seeing the rule, I wonder... * You note one rule…

Yup, I know that "fun" of searching the export. Yesterday we were trying to parse the exported JSON to find any rules with If/Else (...now that we know that doesn't always work as documented :^)

Often someone disagreeing or "going rogue" knows or believes something the rest of the team does not. And, occasionally a person is just argumentative for other reasons. The team discussion will uncover that hidden knowledge so all can benefit from their shared contribution. For the other path, that sounds like a staff…

Thanks, Samuel. I understood that...I thought you meant summaries were not displaying for *your* swimlanes so I wanted to confirm.

If/Else is not available in branches for the Cloud version yet either; just asking in case they get added: https://codebarrel.atlassian.net/browse/AUT-1005 Thanks, again!

Hi @Raju Mandapaka Yes, and I believe that you would need to do so using a web request action to the REST API edit those fields. It is not yet possible to set the Start Date directly during the Create Version action. Here is the suggestion to add that feature: https://codebarrel.atlassian.net/browse/AUT-2027 Best regards,…

@Samuel Prathipaty this is what I see for a company-managed project when using swimlanes by story. I have highlighted where I see the summary.

Hi @Guru Darbar Adding to what John suggests for automation, you may find these examples and sources helpful: * https://www.atlassian.com/software/jira/automation-template-library#/label/all/1453 * https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465 *…

Hi @Bruna Junckes Sant Anna As @Ravi Sagar _Sparxsys_ noted, this isn't possible yet. Here is the suggestion to add a trigger for Project Created to automation, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JIRAAUTOSERVER-177 Best regards, Bill

Hi @John Duffus Atlassian is working on improving/restoring the "dot" menu. You may follow their progress on this item: https://jira.atlassian.com/browse/JRACLOUD-71827 Best regards, Bill

Samuel, is that a Company-Managed (classic) or Team-Managed (next-gen) project? When I use swimlane by stories, I am still able to see the story summary at the top of the lane for company-managed.

Got it. I'd recommend trying the manual rule for a sprint or two, see if that works for the team, and then decide if you want to fully automate it on that last sprint day.

Hi @Евгений Фарсалов At this time, the only way I can think to do this is to export all and then run a script against the JSON to prune to your 12 rules. Maybe use a common naming convention to make it easier. There are a few open suggestions to improve import/export, which you can watch/vote for, or add another…

Hi @Shubham -- Welcome to the Atlassian Community! Do you mean to filter based upon the Due Date of the epic? If so, you could use a hard-coded date to check. Or you can check relative to the current year. For example: project = myProject AND issueType = epic AND duedate >= "2021-01-01" AND duedate <= "2021-03-31" project…

Hi @Maja Bobeta You could do that with an Automation for Jira rule, using a scheduled trigger. Please look at these examples and the documentation for ideas: * https://www.atlassian.com/software/jira/automation-template-library#/label/all/1453 *…

Hi @Rob Wolfe Here is the suggestion to add that feature, and one other to improve rule import: * https://jira.atlassian.com/browse/JIRAAUTOSERVER-83 * https://jira.atlassian.com/browse/JIRAAUTOSERVER-101 Best regards, Bill

Hi, Jason. "No", and that doesn't matter for your use case. You may trigger a manual rule from a specific issue, and within the rule you could use a branch on JQL to process what you need to take action on. Yet you were trying to automate this to save time, prevent errors, etc. That is one reason I suggested the Scheduled…

Hi @Jason Gaines -- Welcome to the Atlassian Community! For a question like this, please consider posting an image of the audit log from the rule execution. That may help reveal what is happening. Regarding your two questions... ...all tickets in the completed sprint to the "Done" (even the 6 not meeting the criteria...…

Hi @Rodrigo Martinez Just to check... Based on your description of the scheduled trigger with JQL--If/Else issue, I would hypothesize this also could happen for a branch with JQL that contains an If/Else. Is that correct? Thanks!

@Rodrigo Martinez thanks again. Such behaviors in automation rules are an example of why I suggested an improved documentation page, similar to the one for the REST API versions: * All components/features on one page, and so more easily searchable * Components identify applicable Jira versions for which they work (cloud,…

Hi @Samuel Prathipaty I answered your question in the thread you noted, using: substringBefore() Best regards, Bill

Hi @Samuel Prathipaty You could use substringBefore() first to truncate off any earlier sizing, and then add on the new story points string. Please look here for more information on that function:…

Hi @Rodrigo Martinez Thanks for your responses and explanations. I thought I understood which parts of automation rules executed non-deterministically (branches, racetrack conditions, etc.) and clearly there is more to learn. If nothing else, this post is leading me to pause on further rule usage for any non-trivial use…

Hi @Ryan McBryde Sending one email for each issue is what @Mark Chaimungkalanont was also suggesting. For that, you would just use the scheduled trigger with JQL, and use another other criteria with conditions before sending the email. If that works for your team (getting multiple emails), you are done! If that gets too…

Hi @Rodrigo Martinez I am curious why the issue you reference is a "suggestion" when this design choice seems more like a defect. Would you please help the community of users understand this design choice? This approach seems to make sense if the result set of a scheduled rule with JQL had to fully match the query or were…

Hi @JRodney Estrada Team-managed projects cannot have multiple boards yet. Here is the suggestion to add the feature, which you may watch or vote for. There is a recent comment (February 2021) from Atlassian about the progress. https://jira.atlassian.com/browse/JSWCLOUD-17371 Best regards, Bill