Bill Sheboy Expert

Hi @jose.matzkin What have you tried thus far? Would you please post an image of your automation rule and the audit log? That may provide more context for the community to help you. Thanks! And, what do you mean by "related to an issue" for the bug? Do you mean linked or something else? And, do you mean the epic of the…

Hi @Ritu -- Welcome to the Atlassian Community! I do not believe you can do "what-if" analysis based upon dates for lower-level issues (story, bug, task, subtask) with out-of-the-box Jira Cloud standard version. For epics, you could use drag-n-drop and issue edit on the Roadmap to see impacts. For more what-if features,…

Hi @Michele Snow Please consider why you are doing those other work items, and how your capacity/availability impacts your team. When the items are necessary for the same effort, perhaps putting them in the same place as the team's work could help others see your capacity/availability, and where they can help. When the…

Hi @Michele Snow Yes, and to Mikael's ideas... When you want to visualize and manage your full lifecycle ("concept to cash"), consider using a single Kanban board for work, perhaps showing feature-level work on a higher scale board. This can support abandoning ideas which do not pan out and the ones which proceed to…

Hi @Lars Schirmer What problem are you trying to solve by implementing this? It would appear you have an expectation of service level/readiness of at least 3 days, and people are not aware of it or not respecting it. Perhaps that is a different problem to address. Thanks! Best regards, Bill

Hi @Igor Strba You can edit an issue's fixVersion field, setting it to a smart value expression. When you select the field, just type in your expression. And, assuming there is only one value in components, you can use your {{issue.components.name}} and add on your date information to build the version name for assignment.…

Hi @Colum McAndrew What type of project are you using: team-managed or company-managed? The type of project will influence what you can do built-in versus not. For team-managed, you could use a scheduled automation rule to set the "flag"/impediment indicator for stuck issues. That would highlight such issues in a light red…

Have you tried to send an email directly from your work account to your personal one (outside of Jira)? That will rule out problems with your personal account receiving emails. Next, I would delete and re-enter the email address in the TO, confirming there are no typos. If that doesn't work, I suggest it is time to create…

Sounds like a good theory. Perhaps check your spam folder of the personal account for those emails.

Great; progress! Okay, now find a volunteer for your external email address, and add them to the TO, keeping yours there to confirm the email sent: myAddress; theirAddress This will confirm it works, and then help you work with the volunteer (receiver) to learn if those emails are getting filtered on the receiving side, or…

Okay...connecting my questions together where I believe John was heading: You are showing the field names on the issue view, and have you confirmed how those match to the custom field IDs you are using in the calculation? Let's try this: * Using the Log Action, please write each of your calculation parameters to the log so…

Thanks! How about this: change your rule to send the email only to yourself with a known good email address, and retest to see if that works. If it does, that narrows this down to possibly invalid email addresses or the receivers consuming/or sending the emails to spam. If it does not, there is a more general issue with…

Hi @Allison Troup Would you please post an image of the audit log for an execution where you think the rule should send an email? That may provide more context so the community can offer ideas. Thanks! Perhaps the rule is triggering and not sending the email due to a timing issue, and so all of the data is not present yet.…

Thanks, @Sam Harding ! This could come in handy, as it appears to support a created variable as a source smart value, leading to generic loop processing or pulling apart just-in-time created lists. Now if variables just had an edit action and Lookup contained all of the issue fields... :^) Keep up the great work! Best…

Linking together these two same questions for this topic: https://community.atlassian.com/t5/Automation-questions/How-do-you-sum-up-story-points-to-the-epic-using-jira-automation/qaq-p/1731595

Hi @Lucy Cookney To perform that math operation on your CoD (Cost of Delay) to determine WSJF (weighted shortest job first), you need to use math operators: {{#=}}{{issue.customField_10081}} / {{issue.customField_10024}}{{/}} or {{issue.customField_10081.divide(issue.customField_10024)}} Please look here for more…

Thanks, Kerrie. This design of unsaved changes for Description has stung our team a couple of times already, where unsaved changes by one person later replaced subsequent edits by other people. The "work-around" seems to be never leave that field with unsaved changes. A better design would perhaps be to abandon/discard all…

Hi @Kasper Sørensen Sorry I wasn't clear...and thanks for catching my error! After you test the Lookup Issues and decide to update the epic, you will need a Branch to select the epic, and then you can edit it. * trigger: when value changes for Team * condition: issue type is not epic * action: lookup issues with JQL of:…

Hi @Pierre VIAU Just to confirm, are you certain the following works as you expect? {{issue.fixVersions.startDate.first}} Fix Versions is a list field, and so the above smart value will return the startDate of the first item in the list, regardless of the order of the values (or the position of the start date in that…

Hi @Monica -- Welcome to the Atlassian Community! This is a similar suggestion for server: https://jira.atlassian.com/browse/JSWSERVER-15631 If you do not see what you need, you may also create your own suggestion. Thanks! Best regards, Bill

Hi @[deleted] ... I am glad to hear that helped. Please consider marking this question as answered. That will help others in the community find solutions faster. Thanks!

Please try the advanced compare condition I noted above, rather than the simple field condition. You may then check the smart value from the trigger {{version.name}} to find the relevant team name.

Hi @l bascle Sorry for the delay in responding. For the second approach I noted above, you could do something like this: * trigger: sprint starts * action: create version * branch: on issues in the sprint* action: edit issue to assign the fixVersion to the newly created version

Sorry, I am confused... * If each team has their own versions to release (from your example: "Sarai-Team Release 6/30/2021"), and * that team's issues are marked with their version *only* and no other versions, * when that version is released, the issues associated to that fixVersion will only apply for that team. * So…

Thanks, @sarai.makni Given what you describe, I suggest you could do this with one rule if you have a known set of teams. For example: * trigger: version released * action: lookup issues in the version released with JQL * if/else condition: with advanced compare condition: {{version.name}} contains the name of a team A*…

I haven't had consistent results with that related issues condition... How about trying a simpler rule, if it meets your use case: * trigger: issue transitioned to Review * condition: issue is a sub-task * branch: for parent* condition: if status is not Selected (or any later status values in your workflow...so check any…

Given these are two list fields (sprint and fixVersion) I can think of two possible solutions, both with assumptions: * With the shown rule, assume there is at least one story with one-and-only-one sprint (the current one), and so add a condition to confirm that before creating the version: {{issue.sprint.size}} equals 1 *…

Hi @l bascle Are your stories in multiple sprints, such as carried over from one to the next? If so, what you may be seeing is because the sprint field is a list of all sprints an issue has been in. Best regards, Bill

Hi @Nikola Grbovic -- Welcome to the Atlassian Community! What have you tried so far? It may help to post an image of your rule for the community to have context to offer ideas. For something similar to your use case, please take a look at this rule in the automation library:…

Hi @Wojciech Klupś Rather than using the condition and branch, you could use JQL to get the sub-tasks which have the assignee value(s) you care about, and if there aren't any then proceed. Here's some information about Lookup Issues:…