Bill Sheboy Expert

Hi @Yaiza Temprado -- Welcome to the Atlassian Community! What have you tried thus far? For example, did you try the solution described in this thread by @Ste Wright using the basic edit functions? If that does not meet your needs you probably have a different use case/need. I suggest: * creating a new question, *…

Hi, Rigo! Thanks for the additional information, and that matches my understanding of your initial question. Jack's suggestion seems like a good approach using Jira. Specifically, I would use a very large monitor (or three side-by-side) showing the three Jira boards. Selecting any one of them would give context to then…

Hi @Кирилл Матвейко Yes, and...to Mark and John's answers... Are you trying to send one email for all assignees (with groupings) or multiple emails (e.g. for each possible assignee)? For each approach, there are limitations. One email: You need to know all possible assignees in advance, and using their user accountId…

Hi @Rigo Ewen -- Welcome to the Atlassian Community! Yes, and...to Jack's answer... Out-of-the-box Jira does not support Kanban board layouts to show such an entire value stream with complex flow across multiple teams. If this is just for a wallboard display on a large monitor, Jack's suggestion seems like a good…

Hi @Gökay Kazdal -- Welcome to the Atlassian Community! The days in column values appear to be computed dynamically for the boards, and so are not a sortable field for JQL. As possible work-arounds, you could investigate the Atlassian Marketplace to learn if there are JQL addons to do this...or you could add a custom field…

Hi @lwilder -- Welcome to the Atlassian Community! I am not familiar with that one as a built-in action for automation rules. Is that something your integration between Jira and Salesforce added to the UI? Perhaps first check the Salesforce documentation to learn if there are recommendations for use with Automation for…

Hi @Ganesh Navale -- Welcome to the Atlassian Community! Yes, and...to what Nic notes. I believe there was a built-in gadget like the Great Gadgets wallboard one, and Atlassian sunset it a while ago (14 July 2021). Kind regards, Bill

Hi @Jesse Ignell -- Welcome to the Atlassian Community! One way to do this is with Components. Create a component value for each team, and adjust their individual boards' filters to only show that component value (and perhaps no component assigned if they pull from a common backlog of work prior to sprint start). Kind…

Hi @SHEHZADALI ISMAILY As the product owner could be creating an issue on behalf of another Reporter, I suggest using the smart value {{initiator}} as that is the person (i.e. user) who triggered the rule, and add a condition to exclude the product owner. Also...the Issue Created trigger could fire faster than the data is…

Thanks for clarifying your use case... Short answer: I do not believe partial matching is possible without calling the REST API. Longer answer: Automation rules have triggers and actions that can access issues, versions, sprints, etc. They cannot access components not already associated to an issue except while…

Hi @Yehoshua Silberstein Pausing for a moment: what problem are you trying to solve by storing the same information in two different fields: a custom field and in a component? For example, is this to support reporting somehow? Regarding your questions... As @Vikrant Yadav noted, you may get all of the available components…

Hi @Jan Zyka -- Welcome to the Atlassian Community! I do not believe there is a built-in dashboard gadget for such a chart. Please take a look in the Atlassian Marketplace for addon possibilities, and then discuss that with your site admin. They may know of other addons/options you already have available. Kind regards, Bill

Awesome! We use that app and it has a much better CFD than the built-in one.

What type of project and board (e.g. Scrum or Kanban) are you using? You may find the project type at the left-side of the view: expand the area and look at the bottom. Thanks!

Hi @Vera Sinnamon A cumulative flow diagram (CFD) displays what you note: the count of items in each status, day by day, as well as the cumulative count of done items. Atlassian's interpretation of this chart is available for both Company-managed and Team-managed projects. To learn more please look at this documentation,…

Hi @EddieCM_Chuang Each gadget type has its own abilities and behaviors. For the built-in ones from Atlassian, it is unlikely those will be updated...given they have not changed for many years. For any ones you acquired (free or paid) from vendors, I suggest contacting the vendor to ask this question. Kind regards, Bill

Hi @kristi gray Yes, and...to John's answer... You may be able to do what you ask with an automation rule. Would you please clarify what problem you are trying to solve? I ask because as you have described the use case, couldn't multiple different clones of the original issue lead to conflicts? That is, to which status…

Here's one that works, using list iteration and smart value, in-line conditions (filtering) with equals(). The spacing and null-handling (including the leading 0) are key to prevent errors in the math operation. {{#=}}0{{#issue.customfield_10063}}{{#if(equals(value, "Option A"))}} + 40{{/}}{{#if(equals(value, "Option…

Hi @Christopher Lebruh I have not used Jira Align before, and after a quick look at Atlassian's information on it, I did not see anything obvious for your use case. You may want to work with your site admin to contact the support team for this one. Kind regards, Bill

My mistake; that one does not work! I'll experiment with it a bit to see what is not working. Until then, please continue, perhaps using created variables to sum up.

No problem and glad to help! For your use case with just a few options, there is a simple way to do this with the match() function. For example: {{#=}} {{#if(exists(issue.yourCustomFieldNameOrID.match("Option A")))}}40{{/}} + {{#if(exists(issue.yourCustomFieldNameOrID.match("Option B")))}}30{{/}} +…

Perhaps try the advanced compare condition, referencing your object and check if it is non-null (not empty) before the edit.

Yes, I think Charlie identified the cause: your rule structure is performing an AND of the two conditions. To still include both, switch to one condition with: summary ~ "September 1" OR summary ~ "August 1"

Hi @Elif Alverson Yes, and to John' question... In the audit log, please expand some of the details sections with "Show more" and post that image. That will indicate which steps in the rule processed, or not. Thanks! My hypothesis: your JQL conditions on the Summary field are not matching as you expect. Kind regards, Bill

Hi @tyrone kimble One way to do this is to copy the rule and change the copy to use a scheduled trigger rule with JQL, looking for open (i.e. not done) Epics where the % complete field is empty. Automation rules can process up to 100 issues (due to performance limits). Let the rule on a schedule until it gets caught up for…

Hi @Brock Jolet You could try using clone issue on each subtask, and then call the REST API to change the parent, as described in the work-around for this suggestion: https://jira.atlassian.com/browse/JSWCLOUD-22718 Please note that with the number of subtasks you have described, to support your workflow, this will be a…

Hi @Debbie -- Welcome to the Atlassian Community! You noted that: I'm trying to automate inputting a Parent start date based on a Child's earliest due date However looking at your rule, the check on date with the condition appears to be the problem, and if you show the details of your audit log, it may confirm this. In…

Hi @Jianquan Zhang -- Welcome to the Atlassian Community! For a question like this, there are several things to check: * What is the purpose and structure of your automation rule? Perhaps post an image of your complete rule to offer some context for the community to suggest ideas. * What do you see in the details of the…

Hi @Darrel Jackson First thing, I do not have an answer for you...and... A teammate asked me a similar question yesterday about Jira Product Discovery: it seems that drag-and-drop ranking and in-line issue create stopped working; what is happening? The reality was that they added a sort-on other than on "rank" and so…

Thanks for that rule image. I note two things to try: After you edit this trigger issue's fields, add a Re-fetch action before you use the Clone action. Next, if you want the email to contain the newly cloned issues information, you may refer to it using the smart value {{createdIssue}}…