Bill Sheboy Expert

Hi @Ben What do you mean by "logically related" for these issues? Can you write a JQL statement to return those issues, based upon the triggering issue and some criteria? If so, you should be able to use a JQL statement with a trigger or branch to get the issues needed for the update. Please consider posting an image of…

Hi @Sam Lehman I tried to reproduce the symptom you see, and could not. I found this defect created recently that seems related, and a fix is in progress (according to the comments). https://jira.atlassian.com/browse/JRACLOUD-76653 Until then, I suggest ensuring that you tab off of each new label entry as they are typed.…

Hi @Ricard Renalias In addition to the suggested improvements to make this information searchable out-of-the-box for Jira, there are marketplace addons which allow searching the Project's Entity Properties. One of those properties is Style, and it indicates "classic" or "next-gen". If you do not want to purchase an addon,…

Hi @[deleted] Please try this one: project = myProject AND fixVersion = myVersion AND status CHANGED AFTER -24h Please see this documentation for other tests around status changing: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/ Best regards, Bill

Hi @tletz24 Just to confirm, you are trying to use the componentMatch() function from the ScriptRunner addon in your automation rule condition. Is that correct? If you try that JQL stand-alone (outside of an automation rule), does it work as you expect? Best regards, Bill

Hi @[deleted] Would you please provide some context, perhaps with an image of your rule? That may help the community to offer you ideas. Thanks! Currently, there appears to be no ELSE structure in the smart value logical processing: https://support.atlassian.com/jira-software-cloud/docs/smart-values-conditional-logic/…

Hi @Sarah Baker Just a hunch here: during your task create in the rule, are you using the field drop-down to set field values *and* using the More Options with JSON, as that is what your image appears to show. If you are not using the More Options, please clear that out (setting it back to the default), collapse the More…

Hi! The fields may have non-obvious naming. How about this: please reach out to the Big-Gantt vendor's support and see if they have experience with automation and their fields: https://marketplace.atlassian.com/apps/1213016/biggantt-gantt-chart-for-jira?hosting=cloud&tab=support If you learn something from them, please…

Hi @Nadav Shamgar -- Welcome to the Atlassian Community! Full disclosure, I am not using that addon product, BigGantt... If the fields you want are accessible as custom fields, you may be able to edit them with smart values. To learn if they are available, find an example issue which has that data and then call the REST…

Hi @Christian Barth [X] -- Welcome to the Atlassian Community! Adding to what Walter suggests, when checking for something which does NOT match a value consider if the field could be empty. Such as for Description. Extending the above example that would be: (description !~ Infosheet OR description IS EMPTY) AND Summary !~…

Hi @Kathi Paquet I am glad to see you figured it out. For future reference, please take a look at this documentation page; it shows examples similar to what you were trying to do: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/ Best regards, Bill

Hi @Laura Potter Yes, and...to what Jack says...There are multiple open defects/suggestions for this issue. You may watch or vote for them:…

Awesome! I am glad that helped you.

Thanks for clarifying what you are able (or not able) to try given the workflow and tooling limitations for your Jira instance. Please try searching in this community for REST API change history to find posts about using those methods. You may also find information in the developer community on…

Hi, Darrell! Yup, that seems correct if issues are moving forwards, backwards, and forwards again in the process steps... Let's pause for a minute and consider what level of detail you need. How complex are your process steps? If you have a relatively simple process (or only care about "in progress" regardless of any…

Hi Carsten, Thanks for that information. You describe using an automation rule to detect the task creation, and the task contains the data you need to set the epic dates, so you could set those dates when the epic is created by the rule. Have you tried this yet? Also I wonder: you note keeping the task and epic dates in…

Hi, Celyn. I am glad you got it to work...and...I have not seen consistency in automation rules of when the quotation marks around custom field names are needed/not needed. The fallback when neither seems to work is to use the custom field ID number instead, such as: {{issue.customfield_12345}} Best regards, Bill

Hi @fmarkman -- Welcome to the Atlassian Community! Please try to add quotation marks around your modifiers and units of measure in the relative date functions: project = "ABC" AND issueType = "CDE" AND status CHANGED FROM "deployed" to "closed" DURING (startOfWeek("-1w"), endOfWeek("-1w")) ORDER BY updated ASC Please look…

Hi @Carsten Wiemer -- Welcome to the Atlassian Community! I am unclear what you are asking...perhaps you could answer some follow-up questions to help the community give you suggestions. * Roadmaps are driven by the Start Date and Due Date fields of the epics * You note when a Task is created, you then also create an epic,…

Hi @Amit Rath It appears you are using the Server version of Jira, correct? If you have the paid addon of Automation for Jira (pro version) you could use a schedule triggered rule to send the issues to Slack: https://confluence.atlassian.com/automation/actions-993924834.html#Actions-sendslackmessageSendSlackmessage Best…

As long as you do not delete issues from your instance, one way to capture "commitment" and ignore other changes is to create custom fields to store "commitment sprint" and "commitment sizing", storing them with an automation rule once the sprint starts. Those values could then be searched later with JQL. However at that…

Greetings! To avoid multiple conversations on the same thread, I am picking up from where Daniel started... Apologies as I should have researched further on that setting before answering. Following this guidance linked below and what Daniel stated:…

Thanks, and wow: I just learned a new Jira feature: boards without projects! (Although, I am unclear why anyone would use this...at least until we have read-only boards for leadership people. ;^) Anyways...I believe I just replicated that defect for sprint closure when investigating this feature. After creating such a…

Hi @Joshua Cotterell As you are using Jira Server version, a couple of options you could try are: * Create a JQL filter to find the issues for currentUser() and then have each person individually subscribe to it * Create an automation rule for each person, on a scheduled trigger, which then uses the {{issues}} smart value…

Hi @Rogelio Vidaurri Due to possible scope changes during the sprint (issues and sizing), the sprint report can show this information and JQL cannot easily do so. The commitment sum is the total of issues in the sprint when it started progress, and completed sum is the total of issues in the sprint when it completed.…

Hi @Kathy Barton You are most likely running into timing/race-track conditions for your rules. The created issue trigger seems very susceptible to this condition...at this time. You could try this to work-around the issue, combining to use one rule. * Trigger: issue created * Action: re-fetch (to fully re-load the issue as…

Hi @Celyn -- Welcome to the Atlassian Community! Please consider posting an image (and/or the smart values) you tried. That will provide context for the community to offer ideas. Thanks! Best regards, Bill

When you clone an issue in an automation rule, you may optionally set some of the fields. Have you tried to clear the epic link as part of that action?

Hi @Hany G I am unfamiliar with that technique/configuration: linking a sprint to a "user as location rather than a project." If you can clarify what that means and how it is done, perhaps that will help lead to suggestions. Thanks! Best regards, Bill

Hi @Alex Sebastián Oyazún Figueroa -- Welcome to the Atlassian Community! It appears you are concatenating multiple JQL statements in that call. Why not just do the JQL all at once? That may rule out any query result issues. project = IC AND created >= "2021-05-17" AND created <= "2021-05-23" AND status = "En Analisis RM"…