Bill Sheboy Expert

Ah, I think this query is mismatched: * Your HR project field only contains the name, correct? * Your System project field contains name, email address, and user name, correct? * But you are trying to match the second one to the first one in JQL. That cannot work. Instead you will need to extract the Full Name to perform…

@AKBAR you seem to have posted these two comments in both threads. Please look at my response in the other one: https://community.atlassian.com/t5/Jira-Software-questions/Jira-automation-for-creating-sub-tasks-not-picking-up-the-smart/qaq-p/1810344

Hi @AKBAR I note two things: * If your rule works, great! No need for further changes. * Otherwise...* Can your story have multiple sub-tasks, as I note your branch is iterating over all sub-tasks of the story? * If you only want to update the most recently added sub-task, please change your branch to "most recently…

Evan, for your second-to-last paragraph above there is a third possibility: debug or audit log rule actions alter information to make it presentable. Your idea of looking at the raw REST API data is probably best when in doubt about what is needed for parsing.

There are lots of those backlogs for the various types and feature sets, allowing more granularity in issues. For projects, there are business, software, and service types (and some sub-types by template, etc.) Please look here for more information:…

Hi @Michael Beatty You cannot combine the math expression and function format like that. Instead you could try this: {{issue.Story point estimate.divide(issue.Story Points).asPercentage}} If you want better control on the display digits, please also take a look at format() Of note, and a hypothesis: I see you are using…

Hi @Lina Yes, and...to what Tessa suggests: Do the start and due dates of your mediums (e.g. Facebook) ever change? If so, you may need additional rules to detect this and update the subtasks which have not yet completed. Kind regards, Bill

Hi @Aleksandar Colic -- Welcome to the Atlassian Community! For built-in feature options to do this you could: * Export the issues to a spreadsheet (or use the GoogleSheets or Excel addin) to calculate the difference between Created and Resolved dates and then display this as a pivot table on Labels. * Use the Resolution…

Hi @thomas.heller And here is the suggestion I added for that earlier this year: https://jira.atlassian.com/browse/JSWCLOUD-21297 Kind regards, Bill

Hi @Rajesh Konda I can think of three ways to accomplish this: * Use the Lookup Issues action with JQL (e.g. project = myProject AND summary ~ "Release" ORDER BY summary DESC) to get the last issue created, and then extract and increment the value * Use a project entity property to store the last value used, and increment…

Yes, I believe that is correct as you do not have JSM (as noted by Walter). By the way, if you decide you want to try this with automation for Jira, you would need the paid Pro version, not the free Lite one. The free one does not have the required trigger you would need: issue field changed.

@ST Kambor-Wiesenberg , sorry I missed following up on your question. I am glad to see someone else in the community helped you do this with an automation rule! Kind regards, Bill

Hi @julio valdez I do not believe that is possible with out-of-the-box JQL features. You could investigate marketplace addon apps to make searching history easier, or investigate Automation for Jira and add a custom field and an automation rule to capture the dispatch time. Kind regards, Bill

That splitting feature appears to be an open suggestion for team-managed projects, which you can vote for/watch to see progress here: https://jira.atlassian.com/browse/JSWCLOUD-18452

Thanks for that info. Perhaps try logging that created variable after it is set to learn if it contains what you expect. Two more things: Re-fetch can help slow down a rule after the create issue trigger, or to reload data after an edit. How are you using that action in this rule? What type of project is this:…

Hi @Chrissy Garnett What do you mean by "We don't [want to] lose that effort"? What problem are you trying to solve? Typically when Scrum teams size work, they use it as a tool to form a shared understanding of the request and the work involved to deliver it. When that practice is done consistently sizes could also be used…

Perhaps that blog post on the research/survey findings could benefit from additional review of the data; it seems to make some conclusions for only a few percentage points of differences for a sample size of less than 2000 knowledge workers...while noting +/- 2% margin of error on the decided confidence interval. For…

Hi @Rob Peterson Would you please post an image of your complete rule? That may provide more context to offer ideas. Thanks! And also, that advanced edit expression you show seems incorrect. You are using a math expression to increment a created variable (apparently), and then treating the asJsonString function as if it…

Thanks for that information, Joe! I reproduced what you saw, as follows: * created three company-managed projects: HMM, AND, IOS * for the HMM project, I added a Scrum board with a filter spanning all three projects * created issues in each project * created a sprint in the HMM project, adding issues from all three…

Vanessa, I checked the Code Barrel backlog (now part of Atlassian) and didn't see this issue. You may want to ask your site admin to submit a support ticket to confirm with Atlassian if this possible: https://support.atlassian.com/contact/#/ Once you hear back from them, please post what you learn so the community can…

Hi, Douglas. If you try to just log to the audit log that custom field's value for a single subtask, does it work as you expect? That would confirm if the smart value can access that field.

Looking at your rule image, is there a space after the quotation mark and before the custom field's smart value, or is that just the way it displayed? An extra space could be part of the problem.

Hi @Mariano Yes, and...to what Gareth and Fabian suggest: Does this ever happen...How do you want to handle the case when all sub-tasks' due dates have changed such that they are now all *earlier* than the before? (And so the Parent is later than the actual set of children.) One way to address this for sub-tasks is to use…

Hi @ahiggins Would you please post an image of your rule? That may give the community some context to help. Thanks! For the attributes of a version, please look here to learn what is available: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/#Smartvaluesgeneral---issue.fixVersions-- And note…

Thanks, Joe. More questions: * For the IOS and AND projects, do they have boards of their own? * If so, are they Kanban or Scrum boards? I am trying to replicate your use case in a free instance to try to reproduce this symptom. 

Hi, Masa. Sorry I wasn't more clear. What I meant was before you use the custom field value in the JQL in the rule, add a Log action to write the value to the audit log. That will confirm what you are testing with JQL is what you expect when you run the rule. After the rule runs, go to the Audit Log, expand the details,…

Yes, as you would not need the groups handling with the REST API. Instead remove the relevant user to create the list, either with if/else structure (for just a few users) or build up the list and then remove it using string functions. How many potential users are getting the email, from which you want to remove one?

Evan, I am glad to learn you got this one to work. Looking over your final rule, it appears you are editing the same trigger-issue multiple times throughout. To avoid "walking over" prior changes, carefully consider if you need to add any re-fetch actions after edits. Remember the in-memory copy during rule execution is…

Thanks for that information, Richard. I seem to recall there are currently problems with automation rules performing the linkages (parent/child) for additional custom issue type levels created with Premium Jira. So if you are able to create and change the type of issues, you may not be able to link them using a rule.

Hi @Amie Walton -- Welcome to the Atlassian Community! Here is the suggestion to add the version report for team-managed projects, which you may vote for/watch to see progress: https://jira.atlassian.com/browse/JSWCLOUD-18610 Kind regards, Bill