Bill Sheboy Expert

Comments

  • Hi @Paweł Jakimiak Yes, and... to what Nic suggests regarding use of the issue moved trigger for Automation for Jira... There are some open defects with that trigger, so take a look in case any of these impact your use case implementation: * https://codebarrel.atlassian.net/browse/AUT-1526 *…
  • Hi @Antoni -- Welcome to the Atlassian Community! Would you please provide more details to help the community give you ideas to try? * Are you using Jira Cloud or Server/Data Center? * Are you using Company-Managed (classic) or Team-Managed (next-gen) projects, or both * What dashboard gadget are you using to display the…
  • Ah... I see some things of note: Please note the scheduled issues returned (in the PM project) and the branch on linked issues returned (in at least the WPEMEA project). Is this a project-level or a global/multi-project rule? If it is project level this will only process items within the scope of the project where it runs.…
  • Ha! You could always request that feature. ;^)
  • Hi Kaitlin, You are missing a set of parenthesis around the user checks. Without those, JQL is assuming something like this; assignee IN (...) OR reporter IN (...) OR ( watcher IN (...) AND updated... ) What you may want is, noting the bold parenthesis I added: ( assignee IN (...) OR reporter IN (...) OR watcher IN (...)…
  • Hi @Kaitlin Meehan -- Welcome to the Atlassian Community! Please try updating your query for the updated check to use >= rather than = ... AND updated >= endOfDay(-1) ... Also, the placement of your OR statements may not be what you are seeking. Are you really looking for things which were reported by a specific person,…
  • Hi @Lee Street How are you indicating a "PO is added" to an issue? Let's say it is a custom field; you could try something like this: project = myProject AND Status = Backlog AND "Story Points" IS NOT EMPTY AND "PO" IS NOT EMPTY ORDER BY Key ASC For a Company-Managed project (formerly known as Classic) you could add this a…
  • Hi John, I am glad those worked, and that Payne's answer helped you with the assignee part of your question. The thing to note with the CHANGED operator is that it does what you ask. :^) So, it can help to make a quick state diagram (and/or review your workflow transitions) to confirm that the query matches the question…
  • Hi @Russ Cable According to the ticket below this was fixed. You need to first enter some time spent and then the other fields appear. There is a demonstration video of this at the bottom of the ticket's comments. https://jira.atlassian.com/browse/JRACLOUD-70213 Best regards, Bill
  • Thanks for that information. Given no errors in the audit log, I wonder if either: * your RegEx is too complex for the rule engine parser to handle * your RegEx doesn't match anything, and so evaluates to EMPTY Maybe try writing with the Log Action to the audit log, gradually building up your RegEx until it stops working.…
  • Hi @Miller Cofield -- Welcome to the Atlassian Community! It appears some of the ideas you note are in progress/pilot for the new Jira Work Management, which seems to enhance business projects: https://community.atlassian.com/t5/Jira-articles/Announcing-the-waitlist-for-Jira-Work-Management/ba-p/1627313 Best regards, Bill
  • Hi @Bob Bolandrina -- Welcome to the Atlassian Community! Is there a way to return the various Link Types used in the results of a JQL? Not with out-of-the-box Jira Cloud. There are probably marketplace add-ons for purchase that can do this. Also, why aren't all the Link Types being used listed in the available choices for…
  • Hi @Tyler Stephens -- Welcome to the Atlassian Community! What is happening when you run your rule? And, what are you seeing in the audit log? Best regards, Bill
  • Hi! For server, aren't both the Lite (free) and Full (paid) versions of Automation for Jira add-ons? So that would need to be installed by the admin first, correct? Best regards, Bill
  • Hi @Áron Would you please post an image of the audit log from a rule execution that should have worked? That may provide some insights. Thanks! Best regards, Bill
  • Fred, I am glad to hear that helped. Here is a related suggestion for improving WIP management that you may want to watch: https://jira.atlassian.com/browse/JSWCLOUD-21297
  • Hi @Yulia Zhyliaieva I am glad to learn you got the gadget to work. What you were seeing with the repeated status values is the individual statuses for different projects, especially Team-Managed (formerly known as Next-Gen). Those Next-Gen ones duplicate the status values for each project...for each status. Hopefully the…
  • Hi @John Corwith Have you tried something like this: project = myProject AND status IN (2,3,4,5,6) AND NOT status CHANGED AFTER -100d Best regards, Bill
  • Thanks, @Ryan Eaglen Now THAT is a curious, and undocumented, syntax. I wonder if it will keep working in the long-term... I also wonder what other undocumented fields are available via that data attribute. I suggest that you ensure the rule details settings are enabled to notify you if that rule starts failing. Best…
  • Gotcha; Please try a rule like this to send a message when issues are moved into progress. * Trigger: issue transitioned, selecting all of your in-progress status values for To Status * Action: LookupIssues on JQL, inserting your project name project = myProject AND statusCategory = "In Progress" * Advanced Compare…
  • Curious.. Have you checked if any workflow, other rules, or scripting post-functions impact either of those fields? Have you checked if Story Points was changed from numeric to a defined-value list? That could explain why 8 (a valid Fibonacci number) would work and why 16 would not.
  • Hi @Fred I cannot tell if you are on Server/Data Center or Cloud version, so... Lookup Issues will work for Cloud version, so your check on the size can work with the JQL you supply. For Server/Data Center, you may want to try a scheduled rule instead so you can check on {{issues.size}} And regarding WIP measures, we also…
  • @Simon Metz , I am glad that helped you. Just to clarify, when you say "title" that isn't a thing in the vocabulary of Jira. Issues (epics, stories, etc.) have a * Summary, providing a short name; * Description, providing the details of the work-item; * Label, providing any just-in-time identifiers the team wants to add;…
  • Hi Carolina, I will try to answer each of your questions. Please let me know if I miss any of them. Ist there a way to list the issues filtering the status = "in progress" and FixVersions.FIX_VERSION_RELEASE_DATE > current date ? No. As I noted earlier, the attribute Release Date is not directly available with JQL. There…
  • Hi Simon, To edit the Epic Name from the Backlog view: * Select the epic pane on the left so it is visible * Select the epic you wish to update * On the right side of the epic, select the drop-down arrow and View epic details, which opens the epic in a browser tab * Locate the epic name field on the right side of the view.…
  • In general, that is not possible. You may change your localization settings for date/time but not the export formats for specific fields. You note not wanting to use Excel formulas when doing the reports. If you use the free Atlassian plug-ins for Excel or Google Sheets, you can pull the data into one tab and process it on…
  • I first learned about create variable with browser searches trying to solve some state management challenges in rules. (You can also solve these with custom fields and entity properties...but those require use of the Re-fetch Action. But, I disgress...) Then I found this article on solving the scoping issue from one of the…
  • Hi @[deleted] -- Welcome to the Atlassian Community! We handle situations like this by adding a custom field named Abandoned. We also update our board filter to ignore abandoned items on the board and in reporting. Then when we decide we do not need an item, we just check Abandoned, move it to "done", and it vanishes. One…
  • Hi @BEN FRIEDMAN I am guessing at your rule structure a bit, so please let me know if this helps... Create Variable can only be set and not edited yet...but, values can be preserved if you handle scoping. Here are two scenarios: * Trigger: ... * Branch: ...* Action: create variable varMyVariable setting it to {{issue.key}}…
  • One more thing to try, @Beatrice_Dutoit If you just need a weekly email / report, you could create a filter, add the fields you need, save it, and subscribe to have it send you an email on a schedule. Please look here for more information: https://support.atlassian.com/jira-software-cloud/docs/save-your-search-as-a-filter/…