Bill Sheboy Expert

Hi @최창환 -- Welcome to the Atlassian Community! Using automation with marketplace addons depends upon how their fields / data are implemented. If they are custom fields with stored data, it is likely you can do what you ask. Please contact your Jira Admin to learn what marketplace addon you are using for checklists, and…

Hi @Ahmad Fikhri Bin Dakhirrudin -- Welcome to the Atlassian Community! The answer may depend on how your team works... * If you created a Jira issue for the "spike", * And your team sized it using your estimation statistic for the board (e.g., time, story points, count, etc.), * Then the issue's progress will appear on…

Hi @Erez Ben-Or -- Welcome to the Atlassian Community! When reviewing an older question like this, please create a new question and then provide a link back to the older one for context. Otherwise only the people following this thread will see it. Thanks! Back to your question... First, are you using Jira Cloud or Jira…

Would you please post an image of your revised, complete rule? Thanks!

Hi @Chad Jensen This appears to be an open defect that needs triage. Please look here, and you can watch/vote for the issue to see progress: https://jira.atlassian.com/browse/JSWCLOUD-25509 Kind regards, Bill

Hi @Bradley Davidson Have you tried using an automation rule to do this? I have not seen or read about any restrictions on creating JPD ideas from an automation rule in a different project. As JPD is often used for portfolio and/or product management, you may want to discuss this with your JPD user community to ensure this…

Hi @Andrea_Lawrence I believe that is the built-in behavior of rules to prevent potential errors/looping: the trigger issue is excluded from some branching scenarios. A work-around is to add another branch to add that link explicitly. This can be done in two possible directions, so pay attention to your link direction.…

Hi @Heidi -- Welcome to the Atlassian Community! When you create an issue in a rule, you may refer to it using {{createdIssue}} to access its fields. If you create multiple issues, you may instead use {{createdIssues}} Those can be referenced in your email. And...once you create the issue(s) you can then branch to most…

Hi @Laura Snoeij Would you please post images of your complete rule and of the audit log details showing the rule execution? Those will provide context so the community can offer suggestions. Thanks! Kind regards, Bill

Hi @Alex The add subtasks action requires an issue to be in scope for you to add them. And so the flow would be... * action: create your task * branch: to most recently created issue* action: create your subtask Kind regards, Bill

Hi @CC There are several scenarios to handle: * issue added to an Epic, and so update that Epic * issue removed from an Epic, and so update that Epic * issue removed from one Epic and added to another, and so update both Epics * issue created and assigned to an Epic, and so update that Epic For the last of these please use…

Hi @Breanna Williams You may need several rules to handle the edge cases around your scenario. Please consider what you want to do in each case, such as... * Issue create: copy Lead to Assignee. This will need its own rule. * Lead is changed by edit/update: should it update the Assignee? * Assignee is changed by…

Hi @Bridgette Dennis Adding to Mark's answer, here is some good free training from Atlassian and documentation on how to create queries like this: https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql…

Hi @Marvin Brand Based on the other solution posts where you were helped, it seems the remaining part you are trying to do is parse the following: name@mail.com|mailto:"name@mail.com] So you only get one email address. Is that correct? If so, you could either use the substringBefore("|") to grab the first value, or use…

Hi @Scott Gillespie The issue key is not changing based on adding after the sprint start. Instead you are probably viewing a report, like the Sprint Report, which shows the changes of sprint scope. Would you please post images of what you are seeing, including comparing the Confluence page to the Sprint Report to confirm…

Hi @Mirmelshtein_ Roi Have you tried using the built-in pie chart for this, with a filter for just your issues, and displaying Resolution? When you select an area of the pie chart it would show the percentage for that section. An example filter as you describe could be the following, substituting in your values: project =…

Hi @MahanthPrudhvi You seem to be describing sending an email report of issues meeting some criteria, and then for subsequent runs of that report, to not send the already reported issues. If that is correct, and based on your criteria, you would need to some how update the issues to indicate they have already been reported…

Hi @Pooja N That is just a trigger to start a rule. The possible uses of it are dependent upon what you and your team need. Some possible users are: * send a report/notification * create a Confluence page * update a field in all sprint items * etc. Kind regards, Bill

Smart values are name, spacing, and case-sensitive, so please try this to see if that is the cause of the error: {{issue.Story points.asPercentage}}

Hi @Tom Scoggin If you write that expression to the audit log, you will find that the rule's html encoding is adding a paragraph around the description. And so the email (or a browser) display is interpreting the results it is adding space before the paragraph. One work-around could be to use remove() to strip off the…

Hi @roxanne sullivan -- Welcome to the Atlassian Community! First thing, you have posted your question to the Jira automation area. Did you mean to post it as a Trello question? If you actually meant Jira...There is no built-in functionality to do that for Jira. I recommend contacting those you have seen doing this, learn…

Hi @Deeksha Pal -- Welcome to the Atlassian Community! First thing, I wonder: why not just import the subtasks from the file when needed rather than add the attachment? Is there a reason you are not doing that? Regarding your question...Using the REST API called from a rule, I tried this with a CSV file, and it does appear…

Hi @Mike Tocci I suspect the answer depends on how that new field/information from the marketplace addon is populated. And in my experience, a field dynamically updated from the addon may not be directly accessible by rules until it changes...and even then, it must be captured in a created variable to use it. First thing,…

HI @Ishan Mandhan -- Welcome to the Atlassian Community! Adding to Trudy's ideas... What you ask may not be possible at this time, as there is an open defect impacting Jira Cloud and Server/Data Center automation where the changelog does not work as expected for the fixVersion field. Please look here for more…

What are the two values used which led to 8.100 for your "done story points" and "total story points"? Those may indicate where there is a problem. And, you may also use the ROUND function to get the precision that you want, and add the percent sign to the end as text. Please look here for more information about that…

You do not describe "why" (i.e., the problem you are trying to solve). Regardless... The suggestion already offered should work, if the different field values are aligned. The reason is that the id values could be different with two different custom fields, and so values must be used. Let's try this: please write the…

Hi @Niklas Borgstedt That approach seems curious to me, and perhaps indirectly related to the actual cause of the problem. Please post images of your complete rule, showing all actions, and of the audit log details showing the rule execution when it does not work. Those will provide context to help track this symptom down.…

Yes, that JQL change looks better. And, if you want only one email that rule would also need a condition to confirm only the last issue changed sends an email. Please note: there could be some timing/race-conditions if multiple issues update too quickly (or slowly) at the same time; remember the rule will run for each…

When I noted this was a work-around, I meant it will order the ideas by the average, but you would still need to select each average value on the matrix/chart view to see them. Another work-around would be to calculate the average and NOT group ideas in the list view...and instead sort by the average scoring only. For…

There are at least a couple of approaches, as I noted earlier... (1) You noted that you already have a rule to sum up the story points for issues in the epic moved to done. Let's assume you are storing that in a field in the epic. You could duplicate that rule so it includes all the issues, not just the completed ones. And…