Bill Sheboy Expert

This appears to be a duplicate of your other question, @Eva Alofs https://community.atlassian.com/t5/Jira-Core-Server-questions/Complete-sprint-move-open-issues-to-active-sprint-not-visible/qaq-p/2604479

Yup, I agree...and apparently similar inaction with the related the accessibility compliance problems with the tool set and feature colors.

Thanks for the reminder, as I ignored the Parent change for a moment. The Child branch type should have worked... This seems to indicate the Parent field is not found correctly for those issues. Let's test that hypothesis: Change the branch to JQL, with this: parent = {{triggerIssue.key}} AND issueType != Epic Also, what…

Hi @Eva Alofs That sounds correct, as that list of sprints to move issues into is the future sprints (or to create a new one). My hypothesis is the designers considered that if active sprints were listed, it would require another confirmation to change the scope of the sprint. The current way helps ensure the team pauses…

Hi @PARISATO Marie-Hélène Adding to the answer from @Derek Fields _RightStar_ What project type are you using: company-managed or team-managed? You may find that information at the lower-left of the page expanding area. For a company-managed project, you may add another board to use Scrum, as described. For a team-managed…

Hi @Tobias Lorenz -- Welcome to the Atlassian Community! Please try changing the branch type, from "Children" to "Stories (or other issues in Epic)" Kind regards, Bill

Hi @kniep Adding the Re-fetch Issue action may not solve the problem if you are doing this only to add a delay. That action helps with trigger-timing issues and to reload data after edits (before other rule actions). I recommend posting an image of your complete automation rule, images of any relevant actions / conditions…

Hi @Dave Furlani In automation rules, the isEmpty function does not appear to work consistently for all field types to detect a cleared field. Worse still, there are appear to be differences for null (i.e., the field value was never set) versus empty value (i.e., the field had a value and was cleared) for some field types.…

You almost have it; the missing part is to select the values for the field. {{issue.Customer(s).value.substringAfter(" - ")}} This will produce a list of values. As you wanted to put these into a text field as CSV, one addition would be this: {{issue.Customer(s).value.substringAfter(" - ").trim().join(",")}} That will…

Hi @Anup Varghese In addition to the other questions the community is asking, trying to help: Would you please post an image showing the backlog? In particular, we want to see the top of the page and showing any issues of the types missing from the board. Would you please post an image of the entire board? This should show…

I have not tried that, and my searches of the documentation and developer community posts did not show examples: https://community.developer.atlassian.com/ Perhaps at least one other (not expanded) attribute must be supplied in the body. Try with no expand and one attribute first to confirm the function is even working,…

Smart values cannot be directly added, except for setting number fields. Otherwise that will produce a text value. For example, {{issue.ITSU Weight}}+4 will instead concatenate the values, such as 10+4 and not 14. Please review the documentation for how to add values, either with the inline or longer form math expressions:…

Hi @Vadym Hrigorash -- Thanks for the follow-up and confirming this approach helped. Please consider marking this solution as "answered"; that will help others with a similar need find answers more quickly.

Hi @Mayuri Murugesu You describe this: I have multiple existing epics in a specified order created. The first epic has tasks created, again, in a specified order that I wish to clone into all the other epics that are created. How do I effectively do this without manually cloning each task multiple times? Using an…

Hi @Paul Fox-Reeks Well done, solving your own question! :^) To save you some time...you may notice the user mentions in your comments show in the Slack messages as Jira account id values, and not with the users' display names. There is no easy way to change those, since the GDPR changes went into effect.…

Awesome; I am glad to learn that helped, and...sorry I did not explain that one better! Here goes, and please let me know if I miss anything: * {{issue.worklog}} is a list of worklog items * {{issue.worklog.timeSpentSeconds}} would then be a list of the logged times, in seconds * We want to add those up, so we add the list…

Hi @Cash Coyne As Trudy notes, the {{createdIssue}} is the one most recently created in the rule...most of the time. There are cases where that will not be the case, such as with issues created within a branch. I recommend posting an image of your rule; that will provide context for the community to confirm if it will work…

Hi @Yannick-Noah Raubuch Yes, and...to Trudy's answer: Although you could iterate over the comments in the trigger issue and add them one-by-one to the newly created issue, there is no guarantee of what order they will be in for the new issue. As your intent is to copy "idea" issues to "delivery" ones, the order of the…

Hi @Christina Patrick What type of project are you using? I agree with you: viewing a range of time with a control chart, and seeing all of the time flow for the issues, seems better than "truncating" and only showing the duration during a sprint time frame. And seeing the larger time range allows observing measures across…

Hi @Jason Chayer Yes, and...to Jack's answer, here are several suggestions to add that feature. You may watch / vote-for these to see progress. https://jira.atlassian.com/browse/JSWCLOUD-25687 https://jira.atlassian.com/browse/JSWCLOUD-17640 https://jira.atlassian.com/browse/JSWCLOUD-21499 Kind regards, Bill

Hi @Christina Patrick Yes, and...to Kian's answer: It is 24h for a day, and not 8h on this report. This can be seen if you view individual items on the chart that have been in progress for a while as you may find some that have greater than 8h rather than converting to days. IMHO, this is one (of many) limitations of this…

Hi @Dion Nijssen -- Welcome to the Atlassian Community! The docs indicate to use milliseconds and your timestamp value appears to be in seconds format. Please add 000 to the end and re-test. https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-worklogs/#api-rest-api-3-worklog-updated-get Kind…

Hi @Sreenatha Reddy J Are you using Jira Cloud or Server / Data Center? For Server / Data Center, please see the response from @BHUSHAN PATIL For Cloud, there is no rule action to complete a sprint. Instead you could use try using the Send Web Request action and call the REST API function to update the sprint directly.…

Hi @Daniel Sim -- Welcome to the Atlassian Community! It appears @Tanguy Crusson answered that same question here: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Post-Insight-in-a-slack-channel/qaq-p/2179495 Kind regards, Bill

Hi @Rees, Ian I have not tried that, however the REST API doc describes adding expand to the request to add things like the driver: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-id-put Kind regards, Bill

Hi @Janne Jääskä The only constraints on the Project Created trigger are the project type: software, business, discovery, etc. To do what you ask, your rule could use conditions and text functions to check if the name met your criteria: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-projects/…

Hi @YAMAGUCHI Shogo_Ricksoft_ Please see this documentation page for that information: https://support.atlassian.com/jira-cloud-administration/docs/manage-priorities/ Kind regards, Bill

Hi @M C Yes, that is possible with an automation rule. What have you tried thus far to solve this need? If you have started a rule, and it is not working as you expected, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing…

Hi @Cristian Casanueva -- Welcome to the Atlassian Community! It seems you wanted to transition the newly created issue, rather than an issue from the trigger. If so, your rule was incorrect, and the fix is to add a branch to the most recently created issue before the transition. Automation rules are very helpful, adding…

Hi @Travis -- Welcome to the Atlassian Community! I am using Jira Cloud, and this worked for me: {{if(issue.worklog.timeSpentSeconds.sum.gt(0),"has logs", "does not have logs")}} I believe those smart values are common between Cloud and Server, so give it a try. Kind regards, Bill