Bill Sheboy Expert

Thanks, Patrick. I took a quick look and didn't find that feature in the public backlog, so it must be captured in the other work tracking for team-managed stuff. __Bill

Hi @Patrick Farley I believe you are using a team-managed project, and so both of those things are the expected behavior. Please look here to learn more about that type of project: https://support.atlassian.com/jira-software-cloud/docs/get-started-with-team-managed-projects/ Best regards, Bill

Before your if/else clause, please add a write to the audit log for the value you are checking: {{issue.updated.convertToTimeZone(issue.reporter.timeZone).format("hh")}} And perhaps also log this value too (please note the format change): {{issue.updated.convertToTimeZone(issue.reporter.timeZone).format("H")}} I recall…

Hi @Yalan Caslen That link you provided points back to this same posting. Would you please update it? Thanks! __Bill

Interesting...I have not tried to use Lookup Issues as an input to advanced branching yet. I probably would have assumed it didn't work and first unpacked that into a created variable for the input. It does make me wonder if this could be a work-around the limitation of only one Lookup Issues being active at once...Time to…

Thanks for the image...and yup, it is not picking the sprint you necessarily want. That is why the sprint triggers help. And...if you do not have future sprints set up, and the current one always has the latest dates, you could use this with your current rule as "sprint" is a list of values: {{issue.sprint.endDate.max}}…

Hi @Jerrod Van First thing, I recommend updating your post to obscure/remove that actual email address. Thanks! Next, I wonder if you are encountering this problem with special characters in the emails address: https://jira.atlassian.com/browse/JSDCLOUD-6319 You may need to experiment or ask your site admin to ping the…

Thanks, Darryl. I frequently forget that one for sub-tasks and end up "re-inventing the wheel" :^) __Bill

Kelli, I do not see your rule, so maybe try posting it again. And the sprint end date is an attribute of the sprint, not of an issue. If you are seeing that from an issue that means you are looking at a different sprint. Using the sprint created or completed triggers can help as they focus you on the specific sprint you…

Hi @Sarah Coles You will probably need two rules to do this: * your rule to push epic changes to their children (e.g. tasks) * a parallel rule which detects the change in tasks, passing that on to their sub-tasks For the new #2 rule, check the option in the rule details to "Allow rule trigger". That will permit the actions…

Hi @Kelli Frattini-Adams I do not have ScriptRunner installed so I cannot help with that. But if you post your automation rule and describe what is not working the community may be able to help you improve it. Thanks! And, what do you mean by "each time the sprint changes"? Do you mean the end date of the sprint is…

Hi @Giorgos Kavvadias -- Welcome to the Atlassian Community! You can do this with automation for Jira (A4J), and what may help is to read a bit about A4J and look at some example rules first. That will give you context before creating your rule(s). So first, please take a look here: *…

Hi @Bud Herz I was unable to find the documentation on this search field, and these two suggestions state it only checks summary and keys: * https://jira.atlassian.com/browse/JSWCLOUD-17348 * https://jira.atlassian.com/browse/JSWCLOUD-18763 One work-around for this limitation would be to build a dashboard showing issues…

Hi @Aisha Kantharia -- Welcome to the Atlassian Community! What do you mean by "time to deliver"? If you mean Lead Time, you could export issues and subtract the created date from the resolved date. If you mean something else (e.g. Build Cycle Time, In Progress Time, etc.), you cannot easily query that information from…

Hi @JG Meillaud _ The "Story Points" field is the relative estimate field used for company-managed projects, and the "Story point estimate" field is the one used for team-managed projects. I suspect you are using a company-managed project. Correct? It may be better to create your own custom field specifically for "Updated…

Hi @BenGreg When you want to add values with automation to a user list field like Request Participants, you will need to use the advanced edit features. Please take a look a this post for an example: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Automation-for-JIRA-Request-Participants/qaq-p/701059 Best…

Hi @Brock Jolet I do not believe that is possible with built-in, nested branching yet...as you can see in this suggestion: https://jira.atlassian.com/browse/JIRAAUTOSERVER-71 I expect this is due to performance issues, as a single project-level rule could easily use a site's full SLA limits with one execution. And that's…

Hi @Joseph Akbrud -- Welcome to the Atlassian Community! I am unclear what problem you are trying to solve with those measures; however, a query like that isn't possible with out-of-the-box Jira Cloud JQL. The reason is the way the sprint field stores prior values and the lack of a built-in indicator for "rolled-over" and…

Hi @Randle Bailey For a question like this, you may want to work with your site admin to contact the vendor directly for help. I believe this is their support page: https://marketplace.atlassian.com/apps/1218151/capacity-tracker?hosting=server&tab=support Best regards, Bill

Hi @Mohini Chandwani You do not show in your rule what you are using to sum up the values, so would you please show that and show an image of your audit log from an execution that does not work as expected? And you may want to look at these two posts, showing ways to do this for parent/children with and without sub-tasks…

Hi @Chris Hamilton -- Welcome to the Atlassian Community! I am observing two things you may want to resolve: * visibility to issues completed which were missed/added after sprint planning; and * process improvement for sprint planning to reduce the number of these items. #2 sounds like a conversation with the team,…

Hi @violeta.marquez How often do you need this information and for how many issues? Just a few? Please look at the issues' history log. A few more...and are willing to experiment with the REST API and JSON, you could call the function to get the change log history and count things in your final status. You may use this for…

Awesome! I am glad to learn that helped. Please note that re-fetch will slow rule processing by at least a second or two. When trying to see if timing is causing this type of problem in the future, consider first adding a write to the audit log with the data you are testing in the condition. If the data is missing (or not…

Hi @Samuel Smiles P Are those issues removed from the active sprint children of an epic? I recall a problem with some sprint reports incorrectly detecting the removal in that case. Please disregard: I just tried that for a company-managed project and it worked as expected. Best regards, Bill

Hi @Owen Guion There are known race-track conditions/defects in automation where the trigger can fire the rule before all data is available...primarily with the issue created trigger. As a result, data like Epic Link may not be populated in time when you try to test it with a condition. The symptom this will manifest is…

Hi @Pablo Bernardo You note having multiple boards per project, and that would seem to indicate having multiple teams per project. Is that correct? * If so, measuring average time in status across different teams' boards may not be a helpful measure. What problem are you trying to solve by measuring that? * If instead this…

Hi @Eric Anthony Trisilla -- Welcome to the Atlassian Community! Yes, and...to Nic's comments: What is an "accepted story"? Seems like an antipattern smell when you seem to indicate your team is using Scrum. Thanks and best regards, Bill

Hi @Dan Chisholm First thing, I'm not support...only another user trying to help. :^) The link you provided is for the Server/Data Center version of Jira, and you appear to be on Cloud. Is that correct? If so, here is the link to the cloud version of the…

Hi @Nicholas Schneider Thanks, and short version answer: * I believe you have uncovered a defect/documentation error * If you are are on a paid license for Jira, I recommend you ask your site admin to submit a defect here and post what you learn from customer support: https://support.atlassian.com/contact/#/ Longer answer:…

Thanks, Dave. I suspect you may stuck if you are trying to stay inside of out-of-the-box Jira to do this, as @Josh_Kochelek__Modus_Create notes about JQL interpreting the query to max-out on the current date for history changes. (JQL isn't a SQL...) If you are doing this query to chart in one of the plug-ins for Excel or…