Bill Sheboy Expert

Comments

  • Hi @andrea price What does "Critical" mean for a work item for your team and how do they normally respond to such items? As individual Jira users could suppress notifications like comments, will the assignee still get the visibility you are looking for increasing if they do not see the comment? Kind regards, Bill
  • Hi @Shiva Ajodhia Would you please clarify what problem you are trying to solve? It would appear you have a custom field called "Days in Column"...or...are you referring to the built-in "Days in column" setting for a board showing the dots for time indication: Show a visual indicator on each card that represents the time…
  • Hi @Fernando Eugênio da Silva I thought the behavior depended upon the fields being compared... For example, when comparing to just a date field like Due Date, EndOfMonth() would work as you describe...but with a field like Updated that is date/time doesn't EndOfMonth() refer to the start of that day's date/time when it is…
  • Hi @Luca Alotto -- Welcome to the Atlassian Community! First thing: is that custom field you are editing with the JSON the same as "CS - Linked Asset - Reference"? If so, you only want to edit the field in one place, so remove one of those...probably the JSON expression. Next, what value are you trying to put into the…
  • Hi @elaine.xu -- Welcome to the Atlassian Community! The default behavior when creating a new issue (like a bug/defect) is to put it into whatever your "not started" status is. For example, Backlog or To Do. Something else is already changing the status to Valued on create, so consider investigating what is making that…
  • Hi @Tim Foster If you are already successfully setting the created variable with "Monday, 15-Aug-22" perhaps try splitting on the comma and then converting: {{varMyDateVariable.split(",").last.toDate}} or use substringAfterLast(", ") to get at the date string rather than split. Kind regards, Bill
  • Rich, you selected the wrong branch type. Please select the one for the stories/other issues in the epic. Thanks, Bill
  • Again, I first recommend trying to get the data into a dedicated field to eliminate the need for parsing. After a quick test, you may only partially be able to solve this as the regular expression parser for automation rules does not appear to implement word boundaries. So you could find "Germany" and…
  • Arnold, glad to hear that helped. Unfortunately the built-in CFD isn't really a "CFD", for lots of reasons, so these are work-arounds to get the chart to display something helpful. (For example, imagine plotting all of the possible data and then creating a display rectangle over the date region you want to see. The…
  • Hi @Paul Dokken You may do that with an Automation for Jira rule. For example: * trigger: issue transitioned to Done * condition: Fix Versions field is empty * action: edit issue to set the Fix Versions to the "Next unreleased version" You could remove the condition if you want to replace any existing value. To learn more…
  • Wow; I am gonna ask your admin to submit all of the defects we find so they get resolved :^)
  • Hi @Marco Maetzler That is an interesting approach as the "Allow rule trigger" option is documented to allow one rule to trigger another through its actions. This seems to imply the issue collector is being identified as an automation rule (i.e. triggering event) via the initiating user... And...that the runaway looping…
  • Hi @Martin Please post images of your complete rule and the audit log details, as that may provide some context for the community to answer. Thanks! Until then, please take a look at this documentation page to learn the format/syntax for math operations in automation…
  • Hi @Prabhu Chilukuri For a question like this, please consider posting images of your complete rule and the audit log details showing an execution which does not work as you expect. That may provide more context for the community offer suggestions. Thanks! Regarding your empty fields in the email body, if you write those…
  • Hi @Rory Gould From what you have described for your use case, you are trying to do this in an Automation for Jira rule. Is that correct? If so, this will not work with that many countries. An automation rule can only have 60 components (trigger, actions, branches, conditions), and your rule would need at least: * 40…
  • Hi @Pedro Webster -- Welcome to the Atlassian Community! Adding to Trudy's answer, the key helper for your use case is the Lookup Issues action to gather issues for one email: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues Kind regards, Bill
  • Hi @Gianluigi Brasili I do not believe you can "inherit" the custom field values, but you can copy them from the parent to the child issues. Please look here for information on the JSON syntax for advanced edits: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ And if you are having…
  • Hi @Eleni Timini Is this a duplicate of your other question: https://community.atlassian.com/t5/Jira-Software-questions/kanban-board-filters/qaq-p/1980337 Kind regards, Bill
  • Hi @Stella Vuong -- Welcome to the Atlassian Community! It appears you are using a Team-managed project with your Kanban board, and have estimation enabled...And none of the issues currently on the board have an estimate. Please check your estimate values for those issues to confirm this. Thanks! Kind regards, Bill
  • Hi @Eleni Timini Adding to what @Rajesh Ramankutty suggests, you could use a quick filter with multiple components like this: component IN (firstComponent, secondComponent) Kind regards, Bill
  • Hi @Gangadhar Dalli -- Welcome to the Atlassian Community! I believe you are correct: since the change was made in 2017 to limit the returns to 100 entries, the only way to get the other entries is using the single issue call with pagination. You may also search in the developer community area to see if there are…
  • Thanks, Rich. Please look here for information about the Server versions of automation rules. https://confluence.atlassian.com/automation/getting-the-right-version-993924597.html Your rule would basically be something like this: * trigger: field value changes for labels * condition: issue type is epic * branch: on the…
  • From the developer community post on this change, my understanding is the UX will still show/use "Epic Link" for now, and automation, the REST API, and webhooks will support both fields until at least 30 November 2022. There will be an updated announcement with more details as that date approaches.
  • Hi @jeffrey.schrik -- Welcome to the Atlassian Community! Perhaps try storing the fixed date using Create Variable, in the format yyyy-mm-dd and explicitly convert to date type when needed: {{varMyFixedDate.toDate}} IMHO, there are some limitations to where created variables can be used: * Functions: works * Smart value,…
  • Hi @Tim Foster There is an open defect for that symptom, which you may vote for/watch here to see progress: https://jira.atlassian.com/browse/JSWCLOUD-18573 Kind regards, Bill
  • Hi @Rich Evers You note using a team-managed (formerly called nextgen) scrum board...and have tagged this question with Jira Server. Are you using Jira Server/Data Center or Jira Cloud? Both versions could do what you ask with an Automation for Jira rule. For Jira Cloud, this is built-in and for Jira Server/Data Center it…
  • Yes, and...I do not believe the built-in field "Epic Link" is supported by the automation trigger Field Value Changed (and that is unlikely to be added with the changes to use Parent throughout the issue hierarchy). One work-around is to use the Issue Updated trigger and use the changelog to detect changes to Epic Link…
  • Ah...got it. Assignee in that context for the to-email-address is undefined, as there is no issue. They are all in the Lookup Issues result. The way to solve this is to get the email address from the lookup, and add a safety check condition with this: * trigger: scheduled... * action: lookup issues... * advanced compare…
  • Hi @Nishit Popat -- Welcome to the Atlassian Community! As you have asked the question, I do not believe it is possible within an Automation for Jira rule. The smart value of interest for your use case is {{issue.comments.updated}} and the comment you want is {{issue.comments.updated.max}} from the list. I can think of a…
  • Hi @Kelli Keith You cannot do that with the out-of-the-box Jira Cloud, dashboard gadgets. Some possible work-around options are: * Use a custom field and an automation rule to divide the fields and then report on that new value. You will need the automation rule to keep the value updated as changes are made. * Purchase a…