Bill Sheboy Expert

Hi @Yael Geffen Yes, that is possible. One way to do that is with an automation for Jira rule. The rule would need to have global / multi-project scope as it spans both of your projects. It could be triggered on a change to any of the fields which feed into your calculation. To get you started on creating your rule, please…

Hi @Nataly Rios Goico I recommend contacting Atlassian Support directly for this symptom. You appear to be the site admin for a paid, Jira license, and so can do that here: https://support.atlassian.com/contact/#/ My reason is after some quick checks of posts and the public backlog, it seems this behavior (add versus…

Hi @Chandrashekhar Kavi This is a known defect, caused by the design approach used for team-managed projects, and it impacts many gadgets and features. Here is the one for that gadget, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JRACLOUD-72282 Some possible work-arounds are to: * use a…

Have you confirmed the link type is correct in your delete action? Issue links have "direction", such as "blocks" and "is blocked by", and so perhaps the type is incorrect. Have you checked if there are any duplicate link types set up, with the same name? That might confuse the automation rule. Next, as this is Jira…

Hi @Nonla KONE You describe your first scenario's rule working as expected. For your second scenario, do you have a rule created yet? If so, please post images of that rule and the audit log details showing the execution. Those may provide some context for the community to offer ideas. If you do not have a rule yet...I…

Hi @Dennis Messemer Have you looked earlier and later in the global admin view of the automation audit log to find any possible causes? There is a known problem of automation rules not respecting the system time zone setting and perhaps the rule causing the changes is shown running at a different time.…

Hi @Maria DePasquale I notice your rule is making two edits to the issue in the same rule. When doing this, please use the Re-fetch Issue action in-between them. That will reload the updated issue data before proceeding with the second edit. Kind regards, Bill

Hi @YUKI HAMAJIMA Company-managed projects use the "Story points" field and Team-managed projects use the "Story point estimate" field. This can be confusing as in the user interface, both are labeled as "Story Points". Kind regards, Bill

Hi @[deleted] You note you are the only person doing QA work and there are 1000+ bugs to manage. I respectfully suggest having a conversation with your leaders and team about the situation as that seems unsustainably. Back to your question... How many other people are on the team who could be transitioning the issues? If…

Hi @Dave W I believe you can use the .html function to convert, as described here: https://support.atlassian.com/cloud-automation/docs/convert-wiki-markup-to-html-or-plain-text-in-jira-automation/#Rendering-HTML However, there are known issues where everything is not converted. There is an open defect on that symptom,…

Hi @Cash Coyne That is curious... I just tested JQL in that format with a Scheduled Trigger, Branch on JQL, and Lookup Issues and all of them worked. Would you please show what you tried? Thanks!

Reviewing that error message, we can see that the values in your Lecture List field have embedded spaces, such as for "lecture 2". And so the JQL for the branch needs to have quotation marks around the smart value to handle that: project = "Magic Open University" AND issueType = Lecture AND key != {{issue.key}} AND…

There are many examples in the community and as a template for projects. I would start with the second one and update the rule, as needed. If you want to build this yourself... For the first approach, please try to write JQL (for an example story) to gather the subtasks you want. (e.g., BE) Then use that with the Lookup…

Well done! And fascinating...It appears the "equals" condition in an advanced compare condition cannot detect that true in the Second Value means Boolean true...And that is why the isAfter() did not work. It must only be a text value for the Second Value! The work-around I just learned is adding a dummy expression for a…

That one appears to be from an Xray Test Management gadget: https://docs.getxray.app/display/XRAYCLOUD/Overall+Test+Coverage Please contact their support from the marketplace here: https://marketplace.atlassian.com/apps/1211769/xray-test-management-for-jira?hosting=cloud&tab=support

That shows the rule could never trigger: you are not using the story point field. If you want to sum the original estimate the rule must trigger on a change to that field.

Thanks for that information. What does your rule do when a sprint completes? It may be possible to trigger on something else and eliminate the board-specific dependency. For example, if you send a report a scheduled trigger could do that for any boards in the project. If instead it does something to the issues in the…

Awesome; I am glad to learn that helped! Regarding branches, I have learned through experimentation, posts from the Atlassian team, and references in the help, such as this one: https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/#Ordering-of-branch-executions For the distinct function, that is in…

Hi @Liz Humphrey -- Welcome to the Atlassian Community! First, as this is a public community forum you may want to remove your company's Jira URL and your co-worker's email address from the post. Next, some questions to help diagnose this: Can you add other users as watchers to the issue? Does your co-worker have a Jira…

Hi @Cash Coyne You are seeing the behavior of branches... * Branches on one-and-only-one-thing (e.g., branch on current issue, on parent, etc.) get run inline, as if the branch did not exist. * Branches which could be on more-than-one-thing (e.g. branch on JQL, advanced branches, etc.) are run in parallel and…

Hi @Cash Coyne The work-around for that account ID behavior of JQL is to use the IN operator and quotation marks. For example: assignee IN ("user name 1", "user name 2", "user name 3") That will leave the names as-is, without switching them to account ID values, for the search. Kind regards, Bill

Hi @Jezza Sutton Adding to Trudy's question: Would you please show the action to create the variable oldEpic? I suspect this may be where the problem exists. Kind regards, Bill

Hi @Damien Davis Are you asking about automation for Jira rules? If so, and there really are only a dozen of them, I recommend: * having the site admin go to global administration and first disabling the rules (not deleting them) * investigate what problems the rules were solving (i.e., their purpose) before removing them…

Hi @Cash Coyne I would not recommend splitting down the request in either of those ways, particularly with the intention of work spanning multiple sprints. Instead I recommend the product owner and team meet with your scrum master / agile coach and learn ways to split requests down into smaller, valuable, releasable chunks…

Hi @Maximilian Neufeld Adding to Alex's answer... Here is the documentation reference to check: https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html And, please check for any stray / trailing commas. In your post about "one of my first tries" there is definitely a stray comma. Kind…

Hi @Suma Bura I am curious: what problem are you trying to solve by doing this? That is, "why" do this? * For example, are you trying to reduce duplication / maintenance effort by combining rules? * Or, are you somehow trying to align multiple-sprint efforts across teams in one project? * Or, ... Knowing the answer may…

Hi @Hitesh Kumar Khatri That appears to be a gadget from a marketplace addon / app. Please work with your site admin to determine the vendor and then contact their support team for help. And...without knowing what that addon gadget does, or who the vendor is, it is difficult to determine if any of the built-in gadgets…

Hi @Hermance NDounga FYI the link you provided is broken. Is this the one you wanted for the known limitations? https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648 And...I just tested and although an example field of Reaction type is returned by the…

Hi @Massiwen Kinzi Adding to Dan's answer... There are no smart values for the project lead / owner information, but you can use the Send Web Request action to call the Jira REST API to get this information. The function to call…

That is comparing the field to itself (assuming that the enddate and customfield_14803 are the same field). What you originally asked was a check on: is the story's End Date > story's parent's End Date. Please try this using the isAfter function, again assuming that custom field id is correct and it is a date or date/time…