Bill Sheboy Expert

For the template issue, if that issue's project is in the scope of your multiple-project scope rule (in the rule details), it can be accessed for use in cloning from one issue in one project. Now, the messy part: my very first post in this thread appears to be correct about the need for the REST API... After some testing I…

As written, that rule cannot work for both Epics and Stories: the JQL conditions you show check if the issue is an Epic and is also a Story. That is not possible. If you write this initially as two rules, you may find how to combine them. For example, the "Epic" test rule would be * trigger: issue transitioned to Done *…

Hi @Victor - Modus Create What is your relationship to the vendor of this product you are recommending? You have posted to several threads in the last hour, essentially recommending this same product, only stating "based on my experience...". As a reminder...when recommending a marketplace vendor product, please ensure you…

These cases work for me with Jira Cloud automation rules. If your rule matches what I have described, I am unclear what else to check. At this point, please work with your Jira Site Admin to submit a ticket to Atlassian Support to take a look at your rule: https://support.atlassian.com/contact/#/

Hi @Abirami Dhanush -- Welcome to the Atlassian Community! First thing, as this is an older thread it is better to create a new question. That will ensure the maximum number of people see it to offer suggestions. Back to your question... With the built-in features, I do not believe that is possible with JQL. Instead the…

You could call get all boards with no projectKeyOrId filter to return all boards and then filter on the matching project id in the results. For example: "projectId": 10991 If you have have a lot of boards, repeated calls will be needed with paging to gather the results before filtering.

After experimenting a bit I confirmed three things: * when the time tracking Original Estimate and Remaining Estimate values are set with JSON, they are always in integer minutes * passing a unit of measure does not alter that behavior * passing a non-integer value causes it to "floor" the value down to the nearest integer…

Update: please see the end of this thread for a better solution. I'm striking-out this one. How about this: remove the divide by 3600 and add the units of measure of seconds: "{{lookupIssues.timetracking.originalEstimateSeconds.sum}}s" I hypothesize there is some truncation happening and this would confirm / resolve that. 

Hi @Denis Rousselle Two possible causes I can think of for this behavior: The get all boards operation with the projectKeyOrId query searches for the provided project name in the board's saved filter: https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-get Does the board's…

Hi @Kedareswar -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud and not Data Center version of automation. Please test my suggestions to confirm they work for your version. Smart values are name, spacing, and case-sensitive. When an incorrect one is used, they evaluate to null and lead to…

Hi @Maxime Have you confirmed the values in the lookup results match what you expect? For example, you could write all of the values to the audit log to check them: original estimate values: {{#lookupIssues}}{{key}}:{{Original Estimate}}; {{/}} Update: please see the end of this thread for a better solution. I'm…

If you have sprint management permissions in both the source projects in the filter and this project, perhaps something is glitched with that specific sprint. Perhaps work with your Jira Site Admin to submit a support ticket to Atlassian to take a look: https://support.atlassian.com/contact/#/

Hi @Gérard Françon -- Welcome to the Atlassian Community! Adding to the answer from @Vikrant Yadav ... There does not appear to be an event visible to automation rules when issues are moved to / from a team-managed project board, and so rules cannot detect this change. It does not even show up as an issue update! A…

Hi @gloria pechacek How many different user email addresses and matches do you need to set the fields: just a few, many more, or more than 200? * If you have more than 200, that cannot be solved using Lookup Tables as that is the maximum number of rows * If you have only a few, such as less than 5 entries, you could use…

I understand that part, and I was describing how to check if all of the relevant issues are "done" before creating the new one. Is your rule working as you expected? If not, please explain what is not working and post the entire JQL statement used in that condition. Seeing those may help explain why it is not working.

Hi @Michał Majsak -- Welcome to the Atlassian Community! You seem to be asking questions that could be solved with automation rules. Perhaps review these documentation and example sources, try to create rules to solve these needs, and if you run into challenges post your rules to ask for specific help with the rule. *…

Hi @Ondrej Doubek No, I have not done what you describe with Jira, and... If you add custom fields for those values to an issue, you could use automation rules to perform the calculations to set other custom field values. Please refer to these documentation and example sources to try that: *…

Hi @Danylo Kobzar -- Welcome to the Atlassian Community! Based on what you described, I would not expect the jira:issue_updated event to fire as you are deleting a link. Perhaps use the issuelink_deleted event instead. Please look here to learn more: https://developer.atlassian.com/cloud/jira/platform/webhooks/#overview…

Hi @Dima Astahov I suspect the answer is "yes", and the data could be obtained using webhooks or the REST API functions. However, and without knowing your specific reporting needs, you may instead want to investigate reporting options from the Atlassian Marketplace rather than replicating the Jira-stored data elsewhere.…

Hi @Terrence Sheflin -- Welcome to the Atlassian Community! Does this scrum board's filter contain multiple projects? For example: project IN (A, B, C) ORDER BY Rank ASC If so, I am assuming those are all company-managed projects. And...does that specific sprint contain issues for a project where you do not have access or…

Hi @Aleh Charnetski -- Welcome to the Atlassian Community! Disclaimer: I do not work for Atlassian or any marketplace vendor. With that out of the way... Please review your marketplace addons / apps to learn if any are associated with this issue's project and have made issue updates. For example... Based on the image you…

Awesome; I am glad to learn that helped! For any attribution, I recommend listing the Atlassian Community as that may help your team when looking for additional solutions in the future. As for me, I'm between positions at this time.

I recall this scenario from an earlier question, and a workaround was to use another rule to save the URL in an custom field in the issue when the Pull Request Created trigger fires. Later, that field could be used, as needed.

Hi @Rabeeh Adwan -- Welcome to the Atlassian Community! Do you mean in a Jira Product Discovery (JPD) project? If so, I believe all date, custom fields added to a JPD project are that type. Outside of JPD, I do not believe that field type exists: they are Date Picker or Date / Time Picker fields. Perhaps someone from the…

For the recurring stories, you may want to use a manually-triggered automation rule to create them. That could be run before / during sprint planning to have them ready before the sprint starts. For the stories that carry-over, perhaps discuss with the team at the retro for each one to see what could be learned to improve…

Hi @Paola Lops -- Welcome to the Atlassian Community! You describe you have "seen all the proposal and solutions proposed by the community about the topic in the question field but they don't work". What have you tried thus far to solve this need? If you have an automation rule which is not working as expected, please…

Hi @Michail Kotantakis For unique scenarios like this, I suggest doing this step by step, writing results to the audit log for each step, to observe when it stops working. That may confirm what the expression / variable contains that prevents split() from working as expected. Also please note... In my experience, the…

First thing, sorry for the long reply as this will take a bit of explanation. You can skip ahead to "Back to workarounds" for more ideas. The error is describing the problem...(in a roundabout way :^) The trigger is for a version, and that provides no issues to the rule: thus the branch on current issue cannot find it.…

Without seeing your entire JQL statement... I believe you want the opposite criteria: search for issues which are not done, and the condition is there are none found.

Hi @jeffrey.kent -- Welcome to the Atlassian Community! If the user stories are incomplete in the sprint, and continuing work in the next sprint, why not just add them to the next sprint? What is the purpose of cloning the issues? What happens to the incomplete issues in the current sprint? For example, if they are marked…