Bill Sheboy Expert

Hi @JD Lobue Assuming no sub-tasks have been picked up yet, you could try the following: * Trigger: assignee field value changed (maybe want to limit to edit, assign, and transition) * Condition: issue type is sub-task * Condition: status is In Progress * Branch: on parent issue* Condition to confirm parent is not yet…

Hi @Patrick Harrold Have you tried to pass maxResults as a query parameter, which is how you do it when calling the REST API using a URL, such as ?maxResults=100 I believe that 100 is the maximum that can be read in one batch, and that to read more you you make subsequent calls by adding paging. For example the second call…

Thanks for the image; that helps! Do you mean issue RW-24 that you have selected? That appears to be a Story, with Sub-tasks. There are normally three levels of issue types in out-of-the-box JIRA: * Epics * Story, Bug, and Task * Sub-task You normally add issue types like Stories, Bugs, or Tasks to a sprint. Any of those…

HI @Daniels Makarenko Are you using a Next-Gen project? If so, parallel sprints are not yet an available feature for Next-Gen. Please see this suggestion to add the feature, which you can vote for: https://jira.atlassian.com/browse/JSWCLOUD-17195 Best regards, Bill

Hi @Grant Crawford Are you using a Next-Gen project? If so, parallel sprints are not yet an available feature for Next-Gen. Please see this suggestion to add the feature, which you can vote for: https://jira.atlassian.com/browse/JSWCLOUD-17195 Best regards, Bill

Hi @Carlo Markaban Are you using a Next-Gen project? If so, parallel sprints are not yet an available feature for Next-Gen. Please see this suggestion to add the feature, which you can vote for: https://jira.atlassian.com/browse/JSWCLOUD-17195 Best regards, Bill

Hi @Meenu Bhutani Are you using a Next-Gen project? If so, parallel sprints are not yet an available feature for Next-Gen. Please see this suggestion to add the feature, which you can vote for: https://jira.atlassian.com/browse/JSWCLOUD-17195 Best regards, Bill

Hi @Chau_Nguyen -- Welcome to the Atlassian Community! Are you using a Next-Gen project? If so, parallel sprints are not yet an available feature for Next-Gen. Please see this suggestion to add the feature, which you can vote for: https://jira.atlassian.com/browse/JSWCLOUD-17195 Best regards, Bill

Hi @Stefan Nerke -- Welcome to the Atlassian Community! The status CHANGED operator uses the history and can show that. Please try: project = myProject AND status CHANGED FROM "first status" TO "second status" DURING (yyyy-mm-dd, yyyy-mm-dd) There are several variations of this, and the date range seems to be the key for…

Hi @Clarissa Klimek -- Welcome to the Atlassian Community! What do you mean by "move a child issue"? If you want to change the child to be part of another epic, you could clear/edit the Epic Link. That would leave the other children unchanged. Best regards, Bill

Hi @Artur Malak Would you please provide an image of your entire rule? That will help the community to provide ideas. Also, have you looked at the audit log for the rule to determine if there were any issues in rule execution? Best regards, Bill

Hi @l bascle Is this what you are trying to do with a rule? * Trigger: sprint created * Action: create version, with the name of {{sprint.name}} Or, change your trigger to sprint started, and then you could set the Fix Version for the included issues after the version is created using a Lookup action and JQL on the sprint…

Hi @Vladimir -- Welcome to the Atlassian Community! That is not yet possible. Here is a link to a suggestion to add the feature, which you can view and vote for if you wish: https://jira.atlassian.com/browse/JRACLOUD-74565 Best regards, Bill

When on the board or backlog view, go to Board Settings under the ... at the right of the page. Then select Columns. Examine the status values mapped to the right-most column on the board. There should be a checkbox for Set Resolution that you can select for this status. If you do not see that checkbox, you are not using…

Andy, thanks for the clarification and details. That helps quite a bit. Have you looked at the audit log for the rule to see what it indicates is happening? That will tell you if the rule is even getting triggered, or if there are other issues. Regarding my earlier comment, it appears that when you clone, the status is set…

Hi @Steve Saxton -- Welcome to the Atlassian Community! You can do this cloning using the automation rules, which are now included with the Cloud version of JIRA. To accomplish what you ask, you would need to split the problem up into parts: clone the parent, and then branch to iterate over the children to clone them. As…

Hi @Noureldin Ali To accomplish what you ask, you would need to split the problem up into parts: clone the parent, and then branch to iterate over the children to clone them. As needed, you can selectively alter fields as part of the cloning. Note that clone will not copy the links, comments, or attachments. Please see…

Hi @Rich Moll I believe the issue is that these are not marked as Resolved. In this case, they should be resolved and your status (disposition) is "won't fix". On your board settings for the columns, find the status "Won't Fix" and check the box to Set Resolution. Best regards, Bill

Hi @Preston Warden You can also do this if you have the automation rules add-on for JIRA server. Please see here for more information about that capability: https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?hosting=server&tab=overview https://www.atlassian.com/software/jira/features/automation Best…

Hi @Javier_Corchado It appears you can only include information about the attachment (name, author, etc.) but not the attachment itself. There is a suggestion to add this feature to automation processing: https://codebarrel.atlassian.net/browse/AUT-460 Best regards, Bill

Hi @Dave Jackson It appears this is not possible yet, and there is an item in the automation backlog to add it: https://codebarrel.atlassian.net/browse/AUT-460 Best regards, Bill

Hi @Andy Tobias To confirm my understanding of your situation: * Do you have a workflow (dev and release), split across two boards for one project? * Or the workflow on two boards on two different projects? In either case, after the cloning, wouldn't you change the status of the item from Done if there is more work to do:…

Thanks for the information @Maxime Stauffer If you click on the audit log entries, it will show the execution of the rule steps. That will help you learn more, such as was the Assignee condition met (empty) in order to proceed. If not, that would explain why the assignment did not happen. Also, there appear to be timing…

Hi @manikanta ch I am using Cloud, not server... When I checked the server documentation, it notes that you should be able to export or import watchers. For import, the user must already exist in your JIRA instance. Please see this documentation for more info:…

Hi @Lily Tran -- Welcome to the Atlassian Community! Please see this question/post for ideas how to do this: https://community.atlassian.com/t5/Jira-Questions/How-to-retrieve-an-issue-attachments-with-the-rest-api/qaq-p/572084 Best regards, Bill

Hi David and John, Two rules sounds like a good way to go, given potential timing issues in a rule like this. Or you could try the following... Once Ticket 1 is created, if you can uniquely identify it (while still inside your rule's scope) add a Lookup Action with JQL to find Ticket 1. Then use that context to add Ticket…

Hi @Matthias Even though not listed in the documentation for the advanced search functions, it appears that the contains (~) for text field doesn't always match. https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/ Try adding a wildcard character to see if that helps: summary ~…

Hi @REJOY KUMAR BISWAS -- Welcome to the Atlassian Community! How are you trying to edit the sprint field? Issues (such as story, bug, task, etc.) are normally added to a sprint from the Backlog view, using either drag-and-drop or right-click with Add to Sprint... Removing issues is the same as above before the sprint…

Hi @Burhan Mubarok -- Welcome to the Atlassian Community! The issues are not showing because the moved-to project (target) filter is preventing them from showing. If they are showing in the backlog, but not on the board, it could instead be an issue of status mapping to the board or the board sub-filter. When you bulk…

Thanks for that information... If the filter returns all of the issues, the next thing to check is if the missing item has a status value which is not mapped to a column on the board. You can check that by going to board settings, columns, and look for the status value. You can also check if the board as a sub-filter set,…