Bill Sheboy Expert

Hi @Sona Evanesyan Here is an example of doing that in the automation template library: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/140671 For more getting started information on automation rules, please look here:…

Hi @Mark Gibson For a question such as yours, it can help the community answer by posting images of your automation rules. Particularly timing related ones. From what I understand, you have an automation rule triggered on field changes, and that rule is also trigged after new issue creation. Do you mean that someone…

Hi @Lesly Cracchiolo -- Welcome to the Atlassian Community! After your branch, and before the transition, have you tried to add a condition to test for the sub-task type you want? Best regards, Bill

Hi @Steve Hooczko I do not believe that is possible with out of the box Jira. Here is the suggestion to add the feature, which you may review and vote for: https://jira.atlassian.com/browse/JSWCLOUD-18812 Best regards, Bill

Hi @LAURA DIAZ BLAZQUEZ -- Welcome to the Atlassian Community! When you know the specific Epics, you can export them with JQL like this, substituting in your project and the epics you want: project = myProject AND ( "Epic Link" IN (myEpic1, myEpic2, ...) OR key IN (myEpic1, myEpic2, ...) ) Best regards, Bill

Hi @Steve Hooczko The data used for the different reports is different, and so some may be accessible by JQL and others not so much... The example report you noted, the "Cumulative Flow Diagram" (JIRA's version), uses issue change history, and that is not all accessible by JQL query. Please see this other community post…

Thanks for that additional information. Two more things to try, and then I recommend submitting a support ticket: * Go to your project reports, and look at the burn down chart. Does it show what you expect? * Delete the gadget from the dashboard, clear your browser cache, exit all browsers, and then try to re-add the…

Thanks for that information, @JIRA Admin In your JSON, you are trying to update multiple items when that JSON only works for one item at a time. What you could do instead is use the JQL in an automation branch, and then update each issue, one at a time. Please see this documentation for more information:…

Hi @Alberson Barbosa That looks like a NextGen project, correct? Would you please confirm? I just tried it for NextGen and Classic and that is working for me, using both counts and story points. NextGen uses Story Point Estimate and Classic uses just Story Point, so if you are instead using a Classic project the values…

Thanks, Ashish. The audit log image you included does not show the rule execution. Please add that image also. Next, please run this query in issues and filters to see the results: issue IN linkedIssues(AK-7, "Implemented By") Thanks, Bill

Hi @Alex Romano Would you please mark your own question as answered? That will help others in the community find solutions faster if they see the same symptom. Thanks! __Bill

Yes, and... Then you may consider using build cycle time (start of work until delivery duration) when the team wants to review historical efforts to help with future forecasting and improvement experiments. __Bill

Hi @Ross LeMere -- Welcome to the Atlassian Community! To help with your questions please consider: * How do you manage defects today, and why? * You note that some of your "reports to upper management" are inaccurate. What is inaccurate about them and how is the information used? You note that you have 3 environments...I…

Yes, and...If this suggestion gets implemented a work-around would be to reset the epic status using an automation rule when an epic is created. I wonder which of these items will be implemented first: the defect or the suggestion. :^) https://codebarrel.atlassian.net/browse/AUT-1959 Best regards, Bill

Hi @Damien_R Thanks for the details of the situation leading to your questions. First thing: for questions like how to organize your work there is no "best answer". What works for your team may not work for another, and how to "fit" your workflow into Jira may be different as well. (1) How do you transfer tasks and…

Hi... I am catching up with your messages... * It appears you discovered that you missed one right-curly brace, and fixed that, in the Lookup Issues * It appears that "implemented by" does not match the name of the link type. Please check that. To help provide context for what is happening, please post images of: * your…

Hi @JIRA Admin If the global rule does not work for you, I am unclear how you can do this with JQL. Note that JQL is not a complete SQL (e.g. ISO SQL), so you have limited control of what you can do. It appears you are attempting to create a redundant web of links between sets of issues across multiple projects, and so it…

Hi @benji78 I am glad that worked for you. To help others find the solution faster, please consider marking this question as answered. Thanks! __Bill

Hi @Shayne Miller -- Welcome to the Atlassian Community! You may be able to do this using automation rules, as the {{worklog.timeSpent}} and {{worklog.started}} values appear to be available. Please see this documentation about automation rules to get you started.…

Hi @Craig Lashley As you noted, that rule will process each issue separately. When you want to process each item separately, use a branch or JQL in the schedule rule. When you want to process them as a set, consider using Lookup Issues. Perhaps something like this: * Trigger: scheduled every 3 days, no JQL * Action: Lookup…

Hi @benji78 -- Welcome to the Atlassian Community! I just tried getAllProjects and it worked for me: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/project-getAllProjects Best regards, Bill

Hi @Dima Lazarchuk Thanks for that information. If you are a vendor / employee for that product, please disclose your association when making recommendations. You may learn more about this in the community guidelines. Thank you.…

Hi @[deleted] Please take a look at the REST API for creating a project to see if that helps you: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/project-createProject Best regards, Bill

Hi @Gautham Hari You are correct that isn't possible yet in Cloud, and there is a suggestion to add it to the REST API: https://jira.atlassian.com/browse/JRACLOUD-36045 I didn't see this anything for this need in the marketplace, and maybe one of the vendors will comment. There is a work-around, which does require at least…

Hi @Tony Dong Would you please mark this one as answered? That will help others find the same solution you discovered. Thanks! Best regards, Bill

Hi @Alberson Barbosa That burn down image does not seem to indicate the sprint is closed. It seems to indicate that there is nothing sized in the sprint using its unit of measure: story points. Have you confirmed the issues in the sprint have been sized? Best regards, Bill

Hi @JIRA Admin Have you tried a global / multi-project rule, and just use the Link Issue action instead of JSON? Best regards, Bill

Hi @Ashish Thanks for that information. I believe your rule may be trying to update the incorrect issues, which is why the audit log indicates what you see. And, you are trying to update a field repeatedly (in a branch) and so replacing the results. How about this instead: use Lookup Issues to populate the custom field? *…

Hi @Colin Sauvanet Do you have a way to programmagically determine which issues go in the version, such as a specific field in the issues? If so, you may be able to accomplish this using an automation rule. Best regards, Bill

Hi @Juan Carlos Blanco Delgado Well done using automation that way! In addition to sending a reminder, have you considered to add a label, component, or flag to the epic in the automation rule? You may create the swimlane based upon those values. Best regards, Bill