Bill Sheboy Expert

Thank you for that information. When you want to merge project issues and want to preserve something like issue status history, all possible status values must be in the target project...even if they are not used any longer. Otherwise when you move the issues Jira will ask you to provide replacement values for each status.

Hi @Mélanie Liguet That is not possible directly from the Jira interface. You could call the REST API to get all filters, including the JQL, and then search for your text in the JSON results to find the saved…

Hi @Becky Drake For a question like this, it helps to post images of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Without seeing your rule, I suspect the challenge is the order of branching and linking. Perhaps something like this…

Hi @Anirudh Nayak -- Welcome to the Atlassian Community! First thing: the rules documentation around regular expressions states it is "based on Java's Pattern class", and others have found not all of the features from that spec work. I find only experimentation confirms what does and does not work. A work-around would be…

Hi @Vladimir Sumilin What problem are you trying to solve by exporting the issue history of status changes? Knowing that may help the community to offer other suggestions. Until we know that...There is no built-in export of the issue history information. You can call the REST API function to get the changelogs, by pages,…

Hi @Ben Koifman -- Welcome to the Atlassian Community! I am not quite following what you are doing, but...have you tried using the {{initiator}} smart value for a comparison in your rule? https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/#--initiator-- Kind regards, Bill

Hi @Jaime Capitel (resolution) I have not found any great resources, only ones improving over time. :^) My recommendations would be: * create a test project and experiment a lot to learn what is possible * look over example rules in the template library: https://www.atlassian.com/software/jira/automation-template-library *…

To create your stopping condition you need some criteria, such as date/time or count. For example, if you wanted to do this by date/time, as scheduled trigger could be used to only run for a certain amount of time and then stop (such as using a condition). For count, you need some way to indicate the count in the issue…

Hi @Kalyan Sattaluri FYI that lookup issues and create variables appear to be "in progress" now for Jira Server/Data Center and they started in March and April, respectively. You may watch the progress on these items: * https://jira.atlassian.com/browse/JIRAAUTOSERVER-53 *…

When you see two (or more) fields with the same name in that list it is likely there are multiple fields with the same name. Please review your custom field configuration as having multiple will certainly cause problems.

Hi @Rupali Kulkarni -- Welcome to the Atlassian Community! Although Jira Product Discovery (JPD) appears to be built upon team-managed projects, I have not been able to use shared custom fields from company-managed projects, or the site configuration, which were not already in the JPD project. That may be different for…

Hi @Troy I responded to you in the other thread. Short version for other readers: this is broken and appears to be a known defect which also appears to have a low priority/likelihood of being fixed soon. Kind regards, Bill

Hi @Troy There are multiple problems, and inconsistent behaviors, for the issue history and list fields like fixVersion, and so you may not be able to do what you ask. I have observed Atlassian closing several defects on this symptom, or moving them to the dreaded "Future Consideration" or "Long Term Backlog" statuses.…

Hi @Adan Ruiz -- Welcome to the Atlassian Community! I do not believe I suggested those functions...I am using Jira Cloud and not using ScriptRunner. You may want to check the documentation or contact for ScriptRunner to learn if that is possible. My reading of the info seems to indicate that is not…

Hi @Andrew Zebroski You appear to be using Jira Server, which does not have Lookup Issues in rules yet, and so your other option is smart value list filtering (which I believe works with Server rules based on other posts). Kind regards, Bill

Hi @Noble Shore In addition to all of the other methods suggested... A simple automation rule could do this. Some things to decide first are: how are you selecting the issues to change, what do you do if the assignee is empty, and where are these issues located (i.e., one project or several). The answers to those will help…

Hi @Adriana Ramirez Yes; I can think of at least 3 ways to do that: * manually create the ones you need, when you need them * import them all at once from a CSV file * create an automation rule, such as on a schedule, which halts after adding what is needed Kind regards, Bill

Hi @Casper What do you mean by "track"? Do you need a list of numbers or to just know the time in status somehow? What would you do if you had that information right now; how would your team behave differently? The answers to those questions may help you decide what you need to solve this. You could start by looking at…

Hi @Marco Atturio From what you have described, you likely have all of the pieces you need to build such a rule. What have you tried thus far to do this? Please note: rules have service limits to processing, so if you have many tasks (or many subtasks per task), the rule could exceed the limits. Please look here for more…

Hi @Günther De la Motte You do not show your actual rule for context (which can help for a question like this) and I hypothesize that you have one or more branches in the rule. If that is the case, please consider... Rules generally execute from beginning to end, in order of the steps, with a couple of exceptions: * The…

If you are creating all 14 issues as children of the epic in one rule, you could do what you ask. Please note that smart values are name, spacing, and case-sensitive, so please try using {{createdIssues}} after the issues are added, or {{createdIssue}} for the most recent one. Here is the key: you are trying link a series…

Hi @Laura Rusenstrom If you look at this how-to article, it includes how to remove all admins from JPD license use in Step 3. You may then optionally add individual admins using group management later, as needed. Kind regards, Bill

Thanks, and a couple more questions... How are the tasks (children of the epic) created: manually, with an automation rule, issue import, something else? How do you know the task order? Specifically, is there information in each task to indicate what any predecessors (or successors) are? If the information is not in the…

Thanks for that information! Here is what I hypothesize is happening: the way you are performing that date comparison is preventing the expected results due to date/time formatting. (Sadly, not all things represented as "dates" or "date/times" are of the same format in Jira.) We can confirm that by changing to use an…

Hi @Cyril James Yes, that seems to match the current situation. Please try using two different browser types to achieve this for the different accounts. Last year I decided to create a free Jira Cloud account and associate my community account with that one...keeping my "work account" separate for administering Jira.…

Currently the only way to do that is to manually review the log for those dates. There is a suggestion to add exporting of automation logs, which you may vote for/watch to see progress: https://jira.atlassian.com/browse/AUTO-539 In that suggestion, someone has suggested using a python script with a browser to retrieve the…

Hi! An unfortunate aspect of knowledge work is often people who excel as software engineers reach the end of a career tree, and so get "promoted" to manager/leader roles...yet, often traits that make someone an exceptional engineer do not align with being an exceptional people leader. This can be unhelpful/frustrating/etc.…

Hi @Víctor Hugo Ortega Tenorio You could look at the audit log for the rule to see the executions. Unfortunately the log entries will age-out and drop off the list after about 90 days. Kind regards, Bill

Hi @alice.choi -- Welcome to the Atlassian Community! What are you trying to automate: * creating the tasks for the epic * link tasks to the epic * updating the description for existing tasks * updating tasks based on something that happened to a "predecessor" * something else? Knowing this will help the community to offer…

Given that, would it be better to use {{issue.timetracking.remainingestimate}} when subtracting all the remaining time?