Bill Sheboy Expert

Hi @Prashant Sultania As a reminder... What's the difference between update and fields? fields is a shortcut for calling update with the set operation. In the example above, calling set for the description field is the equivalent to including the description in the fields section like this: {"fields": {"description":"a new…

Hi @Raj Reddy A board is a view of a project's issues using a filter. If you already have two boards (...and they work as you expect) then you already have the filters. Please look at your board settings to find them. To make the combined filter, just look at your two board filters to learn what separates the issues for…

Hi @Samuel Smiles P Based upon this suggestion in the backlog, the PR author smart value is not available yet with the PR created trigger: https://codebarrel.atlassian.net/browse/AUT-1997 Once the PR is created, is there a REST API function you could call with a web request action from the rule to learn the author? Kind…

Douglas, I am unclear what you mean by editing the time tracking field. Why do you need to do that?

Thanks for that information, Estelle. It seems you have the JSON part figured out, and are also asking about the text formatting. If so, you may want to look over this information: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all To do what you ask, please try this: { "fields" : { "document link" :…

Wow! Watching that video in the ticket, it seems there is also a data/state-management problem as even though it was the view not refreshing, selecting "save" does overwrite the other action's values. This has the potential to mess up rules if someone is doing edits. And if create issue is "bent", what else may be broken…

Hi, John. If you post your current rule perhaps I could offer ideas to help. I just tried what I suggested using the Advanced Branching and it worked to create separate issues for each component in the trigger issue. For example: * trigger: manual * advanced branch: with smart value of {{issue.components.name}} and a name…

Hi @Andy Heinzer Thanks for that candid and revealing information! And, that would seem to suggest that the use of team-managed projects in an instance could cause other non-deterministic behaviors with advanced searches. From the example in this post, if the fields selected in a JQL filter are not available for functions,…

Hi @Ashwini Gunjal -- Welcome to the Atlassian Community! Would you please define what you mean by "Release scope variance percent", and perhaps include an example? Knowing that information will provide context for the community to offer you suggestions. Thanks! Kind regards, Bill

Hi @Douglas Oliveira That is not possible with out-of-the-box Jira features. There may be marketplace addons for purchase to support this, or you could use custom fields and Automation for Jira rules to compute your own interpretation of "% in progress". Kind regards, Bill

Hi @Estelle Decanis -- Welcome to the Atlassian Community! Would you please post an image of your automation rule and of the audit log containing that error message? That will provide context for the community to offer you suggestions. Thanks! Kind regards, Bill

Hi @Dominique Hermens and @Jack Brickey Although doing this type of linking with a rule is possible, rules have a limit of 60 components, so you probably cannot do this in one rule due to the number of created sub-tasks (i.e. 50 sub-tasks). A work-around might be that you use additional rules to have the creation of some…

Hi, Alex! Would it also help if the rule checked the link type for blocking types? Kind regards, Bill

Hi @Piyush_Annadate and @Albert Arul Prakash Rajendran FYI the function sprintStartDateOf() only appears to be available with a marketplace addon and is not a built-in feature of Jira Server's JQL: https://marketplace.atlassian.com/apps/31399/jql-tricks-plugin?tab=overview&hosting=server @Albert Arul Prakash Rajendran if…

Okay, I have reproduced the symptom and it seems like a screen refresh issue in the rule editor. I found that after your step 7, I do see old values staying on the page. If I click up on the trigger (or another non-create-issue action), and then go back to the problematic component, the values are correct. Of note: I often…

Hi @Garrett McCreery Are you selecting to save your changes before moving to another component? I cannot tell from the video. If you are...I do not see any open incidents on the status page for automation so you may want to quickly submit a ticket to support so they can check your…

Hi @steve.humpston I am glad to learn you got the rule to work. Just a heads up: Please note the license level and execution limits for global/multi-project rules if you are using cloud version, so check with your site admin to confirm how many executions you get per month. Kind regards, Bill

Hi @Christine P. Dela Rosa Thanks for the information! My question is: For companies with salary and hourly employees, and which want to experiment with a four-day work week, what have you tried to make the transition...without resorting to 4x10 schedules across the board? Kind regards, Bill

Gotcha, and...Perhaps it's time to chat with your site admin to submit a ticket to support, and confirm if the REST API does/does not support second-granularity, or if this is broken from one of the recent updates: https://support.atlassian.com/contact/#/ Curiously, millisecond and second options are still available for…

Hi Evan, First thing: created variables only exist within the rule where they are created. They do not exist outside. What I meant was you can use it only in that rule. Next, the JQL you mention which uses a smart value cannot be validated *at design time* in the rule editor. That is why that validate button is disabled. I…

Hi @Tijs Tijert I note that the direction of the "blocking" in your condition and your branch are different. Is that intentional? And, if you check your audit log, that may make it more clear where the processing is stopping. Thanks, Bill

Hi Jason, I missed that you were on server with my first post. Sorry about that! Please take a look at the alternatives that Darryl posted for some ideas on how to do this with your version. I'd also direct your attention to where he asks: what problem are you trying to solve? Knowing that context may help the community to…

Sorry I could not offer more help...Here's an idea: as you appear to be on the premium license level, work with your site admin to submit a support request to Atlassian to provide documentation with such comparisons. If they do not have these, the conversation may help get some specific concerns answered.…

Awesome! I am glad to learn that helped.

Hi @Michael Razey To help clarify what you are trying, would you provide images of: * what is the JQL for your scheduled trigger * what value are you setting to the created variable, childFixVersion * what value are you setting to the edited field, Module Version(s) Of note: I see in the log that many issues are getting…

Hi @Alex Sanda I believe with that trigger you may use the {{project}} smart value. Here are the documented attributes for it: https://support.atlassian.com/jira-software-cloud/docs/smart-values-projects/ Kind regards, Bill

Hi @Alexey You can conditionally add that parent information using the conditional-logic features, as described here: https://support.atlassian.com/jira-software-cloud/docs/smart-values-conditional-logic/ Kind regards, Bill

Hi @Yasser Alattas Adding to Nic's suggestions, you may want to review this post which describes some steps and things to watch for in such a conversion/move between project types: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/ Kind regards, Bill

Hi @faisal khan -- Welcome to the Atlassian Community! JQL is not a SQL, and so it does not support joins, aggregate functions, and other such features. It is filtering tool to support reporting, issue selection for boards, etc. There are marketplace apps for purchase that extend the functions of JQL which may make this…

Hi @aagrawal If your branch has JQL or could return more than one issue, you cannot use a created variable in this way. The asynchronous processing of branches would repeatedly create/destroy the variable and you would get nothing. Please see this article for more details on this (particularly in the post's…