Bill Sheboy Expert

Hi @Edson de Souza Ferreira Filho -- Welcome to the Atlassian Community! Adding to what @Vero Rivas noted, here is the suggestion to add parallel sprints for team-managed projects, which you may watch or vote for: https://jira.atlassian.com/browse/JSWCLOUD-17195 Best regards, Bill

Hi @UI17CO14_Ekansh -- Welcome to the Atlassian Community! The update user method was listed as experimental in the REST API v2 (and so changeable without notice), and it does not appear to be listed in v3's supported methods. What is the method you are calling? You may want to check in the developer community for other…

Hi @prashantgera For this one you may want to submit a ticket to Atlassian support directly. You should be able to do that as site admin for a paid license: https://support.atlassian.com/contact/#/ Best regards, Bill

Hi @Rob Horan One possible cause of this symptom is when using a team-managed project (formerly called next-gen) and the team has created a custom field which duplicates another field's name. If this is a team-managed project, please check if there are 2 Resolution fields in the project. Best regards, Bill

Hi @afsaneh rad Often when people mention using "Scrumban", they do not mean what Corey Ladas did in his 2008 book on this idea. More often they mean "Scrum, but..." (i.e. we use Scrum, except we don't do the following...) or they mean "Kanban, but..." (i.e. we use <X> interpretation of Kanban, except we don't do the…

Hi @Ryan McBryde Unfortunately, there is no rule-defined looping structure yet for automation, to span the possible assignees. I can think of two ways to do this if-and-only-if you have a defined list of possible assignees. * Simple and fast, but maintenance heavy: Create a separate schedule rule for each possible…

Hi, Jeffrey. I am glad to learn you got it working. The "size|0" adds a default value of zero when no issues match the JQL for the lookup. I have seen problems where this can collapse to null, and so cause issues in rules. So I add it for a bit of "belt and suspenders" insurance. :^) __Bill

Hi @Jeffrey Bistrong I think you are close, and just need a few adjustments. A scheduled rule with JQL runs the steps after the trigger for each issue found, so it may be getting a bit of collision on the issues to check. How about something like this below... Please check the names of projects and issue types to confirm…

Hi @Allison -- Welcome to the Atlassian Community! Noticing that you are on Jira Server, the Lookup Issues action is not available there...it is a Cloud feature. Your equivalent for Server is {{issues}} Please note the plural. The syntax will be basically the same as the recommendations to use Lookup Issues, just…

Gene, for some timing issues, the action Re-fetch can help. For example, when triggered on issue create I usually put a Re-fetch after the trigger: the API call from the rule engine seems to catch the event before the complete issue is available. And Re-fetch thus slows everything down a bit (i.e. seconds slower). For your…

Hi @Gene LaMantia This type of rule pattern has racetrack error/timing implications. You noted images of two different rules in your post triggered on Value Changes for Clone Status, and indicate the rule has a sibling rule in the other project. I recommend pausing first to identify each rule which could be triggered on…

Hi, James. Thanks for clarifying. I'd note whatever works for you, works for you. Other teams need other things to manage defects collaboratively as they share work transparency, accountability, and delivery. If you are indeed working solo, maybe just add a label when you have reviewed issues. The absence of the label…

Hi @Bruce Goodman (Engineering) -- Welcome to the Atlassian Community! Multiple boards for a team-managed project is not available yet. Here is the suggestion to add that, which you may vote for/watch. In February Atlassian added a note indicating they do not expect to work on this for at least the next 6 months.…

Hi @James Hudson Have you paused to consider how you and your team perform intake, defect triage, and expediting, and use Jira to manage that with a board/process? You could enhance that using Automation for Jira rules to transition issues based upon disposition to the appropriate support tier/team. Best regards, Bill

Hi @Toni Matković -- Welcome to the Atlassian Community! They are currently working on re-adding/enhancing that function; you may watch/vote for it here: https://jira.atlassian.com/browse/JRACLOUD-71827 Best regards, Bill

Hi @Swaroop If you have the Automation for Jira add-on installed, you can do this. There is a free Lite version and a paid Pro version; both should work. Please look over these sources to learn how to do this: *…

Hi @Peder Alm I believe the short answer is, "no". You would need to make a second call, perhaps with /search using JQL for those linked issues and return the key and fixVersions to join the results. Best regards, Bill

Hi @[deleted] Marco's suggestion will help when the trigger is for the field you wanted to watch, such as Field Value Changed: Description. There are small number of fields for which rules cannot detect a change. If you explain the specific field you want to watch, the community can help confirm this for you. Thanks! Best…

Hi @Andrei Pisklenov _Actonic_ Thanks for your post. How does your lead time chart support something like customer-defined, percentile lines, such as 50%, 85%, 95% for the sample? Having that feature helps teams see if they can meet a service fitness threshold, improves predictability forecasting, and helps reduce…

Awesome! I am glad to hear that worked for you, Andres. Please note well: When using a "Mother of all boards" remember to use it as read-only, for visibility purposes. Specificially, avoid moving things on that board; instead allow the source teams move issues on their own board. Often summary/overview boards like this…

Hi, community! That sounds like this existing defect, which includes a suggested work-around: https://codebarrel.atlassian.net/browse/AUT-2171

Hi @Bud Herz There is an edge case this query will not find: * defects (bugs) discovered, and logged into the backlog * which were not worked on in a prior sprint, and * which were selected for work *during* sprint planning Those defects were not added after sprint start, and so are not scope change. When you need to…

Hi @Michael -- Welcome to the Atlassian Community! I am unable to determine from your post which test managment add-on tool you are using. You may want to find that product name, and then go to the marketplace site for the tool to contact the vendor's support on this issue:…

Hi @serge calderara Did you check if the saved epic name (in the epic) has any extra spacing characters which could cause a mismatch? Best regards, Bill

Hi @smelnikau -- Welcome to the Atlassian Community! The example rule you note is possible for Jira Server/Data Center version when you have the Pro version of automation for Jira: https://confluence.atlassian.com/automation/actions-993924834.html The reason you need the Pro version is that the Link action is only in the…

Roland, I am glad to hear that worked for you. Between the UI/UX, REST API, and smart values, I often check the names with the technique I sent you when something doesn't seem to work as often it is a name mismatch. Best regards, Bill

Hi @Mayur Patankar Did you post this one in the correct thread? That suggestion seems unrelated to the question about an automation rule closing sub-tasks. Thanks, and best regards, Bill

Hi @Hany G What license level of Jira Cloud are you on: free, standard, premium, or enterprise? Have you tried to copy the rule and run it individually in the project (as a project-level rule) for the most recent change? That would help know if this is a permissions issue. If you remove the recently added project from the…

Hi, John. I guess I'm not following what you suggested, so "maybe" ;^) I thought you were suggesting this: * Trigger: scheduled on JQL * Advanced compare condition: for the date check * Action: lookup issues ??? * Action: send the email using lookup I was noting that after the scheduled trigger, everything else in the rule…

Hi Shawn, Please look here for an example of calling the REST API with curl. This example is for JSM and the ideas work for Jira Cloud. https://community.atlassian.com/t5/Jira-Service-Management/REST-API-curl-example/qaq-p/1486907