Bill Sheboy Expert

Hi @ohad.oliver I do not believe that is possible. Jira and Slack have different users (and user id values), so to do what you would ask you would need to somehow add the desired Jira user account ID in the message, and perhaps parse that out with an automation rule. That would be quite cumbersome and error prone to type…

Thanks, that helps! I misunderstood the language in your question to mean moving the story to "done", not just to transition it for the "in progress" steps. In that case, @Stefan Salzl has you on a good track with using Lookup Issues with JQL and checking {{lookupIssues.size|0}} to determine when all of the relevant…

Hi @Deepika singh Yes, and...to Jack's suggestion: I recommend using the Kanban sub-filter to further refine what you want to see for completed work. For example, this sub-filter only shows the items completed during the last business day. That can be helpful for teams which have a daily Kanban standup to review their…

Hi Tim, Thanks for that info, and there is definitely no way to call a rule directly from another yet. Instead the expectation appears to be to create the conditions in issues which lead to triggers happening...and so decentralize the work. Use of the created variable is what I was wondering; if you have already considered…

Hi @Jakub Stephan -- Welcome to the Atlassian Community! Have you looked at the other values for Project Template Key in the documentation, as your value does not seem to match these? https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-post I have not tried this, and I…

Hi @Jim Copeland Would you please clarify your use case? Are you trying to report: * any issues which have not changed status ON the third business day (i.e. issue appears only on one report for a given status) * any issues which have not changed status IN AT LEAST three business days (i.e. once the issue appears on the…

Hi @Saumya Singh -- Welcome to the Atlassian Community! The answer depends upon what you mean by "report", what information you want to communicate, and to whom. I recommend considering your answers first, and then... For other than basic reporting to other Jira users, you may want to search the Atlassian Marketplace for…

Yes, that is what I am observing with my Jira Cloud instance. I could not find more Atlassian documentation on the gadget to confirm the intended behavior. My suggestion is: * create a test dashboard * add the roadmap gadget and select all projects * observe the behavior * adjust the project setting to pick one you know…

Hi @Michael Oltmans Looking at your rule, a couple of things to note: * Branches which could process more than one issue always run asynchronously. Per the documentation, there is no guarantee the branch will complete execution before the other steps of the rule finish. Branches which absolutely evaluate to…

Hi @Peter Yoon Unfortunately what you describe is not possible with out-of-the-box Jira features. Which I find quite disappointing as all of that information is in there...we just cannot get at it without: * purchasing a marketplace addon app, or * running the REST API or webhooks repeatedly to pull out the data for…

Hi @Jeff Toppall Do you mean the built-in roadmap gadget for dashboards, or a marketplace addon one? When I tried this the built-in roadmap gadget displayed the last 50 fixVersions, by release date, that were not archived or released. So it appears to truncate and not support pagination. Kind regards, Bill

Hi @Giada Ermacora If you are trying to find Jira mentions in the comments, rather than just an email address, please note that mentions appear in comment body as: [~accountid:the_users_id_value] Here is a mention! Please consider searching for that expression in those cases using match() rather than a JQL…

Hi @Tim Foster What options to restructure your rule did you try that might solve this? The 60 component limit in a rule does cause challenges, some of which can be solved with loops and advanced branching. Kind regards, Bill

Thanks and I understood that from your picture. I was asking: why would the other subtasks not need to also finish before marking the story as "done"? Is your intention work would continue on the other subtasks even though the story is marked as "done"? If so, measuring what you describe as cycle time would be inaccurate…

Hi @Jennifer D_O -- Welcome to the Atlassian Community! What product is this for (Jira, Trello, etc.), and are you using a marketplace addon for the due date reminders? I am not familiar with a built-in feature of Jira to do this. I have seen teams use either a saved filter subscription or automation rule to send reminders…

Hi @George Stamos Would you please clarify something about your use case? That may help the community to offer you suggestions to help. You describe a need to move the parent story to "done" when a subset of the child subtasks (e.g. the orange ones in your picture) are all "done". What work do the "blue" subtasks represent…

Hi @Francesco La Bianca Thanks for the images of your rule and audit log. I do not see anything that would clear the description, or prevent its copying. This symptom could be a timing problem where the source issue is deleted before the clone completes; you could test that by adding a Re-fetch action after the Clone and…

For the built-in Σ fields fields I think "filter results" is the only option...Perhaps not with out-of-the-box gadgets for many common visualizations. What are you hoping this would look like: as single number by epic, a time-series, etc.? Perhaps post an image of your desired Excel chart to see if something springs to…

Hi @[deleted] When using the Advanced Issue Search and adding that column, I can see it in a search/filter results. What do you see when you try to add that column to the view and then save your filter? Kind regards, Bill

Hi @Brandon Taylor -- Welcome to the Atlassian Community! That is curious...What type of gadget is this for: a built-in, marketplace addon, or something you built yourself? The only time I have seen that symptom was when the gadget cached the selected filter when it was added rather than using the "live" copy of the filter…

Hi @Savvier Dev There is an open defect for that symptom, which you may vote for/watch to see progress: https://jira.atlassian.com/browse/JRACLOUD-78476 Kind regards, Bill

Hi @Francesco La Bianca -- Welcome to the Atlassian Community! It is not possible to clone attachments with an automation rule using the built-in features. There is a suggestion to add this feature: https://jira.atlassian.com/browse/JIRAAUTOSERVER-150 You also note a problem copying the description. Would you please post…

What were the Jira permissions for the account you used to create your API token? And does that account have permission to transition the issues? If that is not it, I recommend checking in the Developer Community area to see if someone has an answer and work with your site admin to submit a ticket to Atlassian for input on…

Awesome! I am glad that worked...particularly because as automation is improved I can imagine some alignment of features between Cloud and Server/Datacenter: * Server / Datacenter gets Lookup Issues and Created Variables... * Cloud gets the "bulk handling" added to Branch and Scheduled Trigger... Have a great day!

Hi @systems-intern Please try to keep your responses to one thread of conversation. That will help others see if there are multiple approaches to solve the problem. Thanks! And thanks for noting you are using the Server/Datacenter version. Please try to include that information when posting questions as the different Jira…

To do what you ask, you will probably need to use branches and/or Lookup Issues on JQL to match the issues to be linked. Once those issues are visible to the rule, you can type in smart values in the Link Issues action. That is described below the field in that action for the rule editor.

Sorry, I was clearly thinking of something else when I first answered...assignee is not a list (and so does not use array functions). This is better: { "fields": { "QC": { "id": "{{issue.assignee.accountId}}" } } }

Thanks, @Rose Eliff Yes, and... I often find people currently working in software engineering have no experience with root cause analysis, 5 whys, differential diagnosis, experimentation, and other problem-solving methods. It is no wonder they sometimes rush to "put out the fire" before understanding the problem/conditions…

Your first paragraph is interesting to me: I thought when the "bulk handling" option is selected for Server/Data Center version the branch executes once and not for each issue. If for each issue, calling the REST API n-times may not be what you want! I recommend confirming this with an experiment inside that branch with 3…

Hi @Matias Delarrivat Does this issueType's workflow have any transitions which require specific permissions/group membership which may be preventing this transition? Kind regards, Bill