Trudy P Claspill Community Champion

Hello @Santosh Panigrahy Welcome to the Atlassian community. With what type of project are you working? That information can be found on the View All Projects page under the Projects menu. How do you identify that an issue is in a particular team's queue? Is that based on the Status of the issue, or on some other factor?

@Senthil V Please show us the rules that you have created. Are you trying to use a single rule to clone a Feature, its child Epics, and the Epic's child issues?

Hello @Eventbuizz Does all the work by both Development and QA need to be done to consider the issue complete at the end of a sprint? Are you working with a Company Managed project or a Team Managed project? I recommend you give some consideration also to reducing the number of discreet statuses you are trying to use. Do…

Hello @Alexander Jakovenko Welcome to the Atlassian community. Are you using a Company Managed project or a Team Managed project? Look at the lower left corner of the screen while viewing the project. You should see a message that says the project type. This issue was specific to Company Managed projects. If you are using…

@traciearls Review the answer provided by @Andy Heinzer 

Hello @lethabo.mahlakoana What event should trigger that notification? How would you decide that the Assignee indicates the notification should, or should not, be sent? Have you considered creating an Automation Rules? https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Hello @Eventbuizz Are the teams using scrum boards or Kanban boar Are you working with a Team Managed project or a Company Managed project? The answers to those questions will impact your options. A given issue type can have only one workflow applied to it a given project. You could consider having a primary issue that…

FYI - the other post mentioned by @Senthil V is https://community.atlassian.com/t5/Jira-Software-questions/Cloning-Epics-including-stories-Jira-Automation/qaq-p/1969797

Hello @Senthil V The thread on which you have posted is quite old, and has an Accepted Answer already. Please start a brand new Question to get help with your issue. In your Question post images that show your complete Automation Rule. If you think this current post is relevant, include a link to it in your new Question.

Please show us the rules you constructed. When I said that there would need to be two rules, that is because the steps to achieve your goal of checking both subtasks and linked issues will be different depending on whether it was a subtask in the HCP issue that transitioned or a linked issue in HD that transitioned. Here…

Hello @Michael Ayers I have so far not been able to reproduce your problem in a Jira Software DC v9.4.11 instance. When I use the same functions with a Date Picker custom field I get the expected results. I did not have to use the format function. Additional debugging you can try with Log actions is to print segments of…

You shouldn't be adding a Validator. That would make the field required. It is more likely that you need to remove a Validator. Let us know if you have additional questions. 

adding to this... The issue type hierarchy in the Jira Standard version is Epic (level 1) |-- standard issue types; i.e. Story, Bug, Task (level 0) |-- sub-tasks (level -1) Issues in the same level can not be made parents of each other. An Epic cannot have another Epic as a child issue. You can convert an issue to an issue…

Hello @Sílvia Aragão Muniz Welcome to the Atlassian community. What do you mean by different "accounts"? Do you mean that when you access these projects you are accessing different Jira instances, where the underlined portion of the following URL is different depending on the project you access?…

Hello @Beth Moore Without using Automation Rules for this the options are: 1. Create a CSV file that is a "template" of the issues, and import that CSV file each time you need a new copy of those issues. 2. Use a third party app. There are a few that support cloning of existing sets of issues. Here is a search from the…

Hello @SUVARNA Dixit @suvarna dixit As you noted, in the Field Configuration the Sprint field is locked and cannot be set to Required. That means it likely has been set to Required through a Workflow Transition Validator and/or a Workflow Transition Condition. Is the project a Company Managed project or a Team Managed…

Hello @Michael Burns You will not be able to achieve your goal in a JQL filter without a third party app. What you need is something like this: project in (CV, TRR, TMS) and issueLinkType IS NOT EMPTY and issue in onlyLinkendIssueOf(project in (RS, RHV, TMSHELP) and issueLinkType IS NOT EMPTY) ORDER BY created DESC The…

Hello @John Carlo Pattaguan Review the details again. The limit depends on the operation. maxResults is the maximum number of items that a page can return. Each operation can have a different limit for the number of items returned, and these limits may change without notice. To find the maximum number of items that an…

Ah, no. @Matt Parks 's suggestion works too. @Matt Parks you should make that a separate Answer so you can get credit for an accepted answer. :-)

Did you apply it to every transition into a status where you want that information required? For instance the Ready For Release status has two arrows/transitions pointing to it. That Condition would need to be applied to both.

Hello @Juan Manuel Alarcon Castrillon Welcome to the Atlassian community. You can't block status transitions using Workflow Properties. Can you show us the diagram for the workflow you are trying to modify? If you currently have Global transitions into all status like this (All --> status) ...you would need to modify the…

Hello @Lindsey Magee Welcome to the Atlassian community. Can you show us the diagram for the workflow you are trying to modify? Can you show us examples of what you have tried for Conditions and Validators? If you have multiple transitions to a given status, you would need to ensure that the Condition (or Validator) is on…

Hello @Claudia Rebeca Jimenez The "Simplified" workflow is not an actual named workflow. Rather it is a type of workflow that follows certain constraints. https://support.atlassian.com/jira-software-cloud/docs/use-the-simplified-workflow/ If you have a board that reference just one project that you want to change, you may…

Hello @Sridivya Penmetsa Welcome to the Atlassian community. What is the motivation for changing the way you are currently working? What problem are you trying to solve by considering using Epics for grouping unplanned work?

Hello @Michael Burns Can you clarify your requirements? You have issues in a Service project. Are you limiting your query to just one Service project. The Service issues are linked to issues in 1..n Software projects. Are you wanting to get all Software issues that are linked to any issue in the Service project? Or are you…

The structure is Issue Type Screen Scheme - project gets only one of these Issue Type Screen Scheme contains a mapping of issue types to Screen Schemes. All issue types might use the same Screen Scheme, or you may have different issue types using different Screen Schemes. An issue type can be mapped to only one Screen…

One more series of questions: Can the HCP issue be linked to other issues in the HCP project itself? If it can be linked to other HCP issues, will the Link Type used to link the HCP issue to the HD issue be unique and not used to link HCP issue to other HCP issues? I believe you will need two different rules. The final…

Hello @Brandon Forslund Thank you for those screen images. That is very helpful. Upon completion of a sprint only the issues in the column farthest to the right on the board will be considered "complete". It doesn't matter what the actual status of the issue is. It only matters if that status is mapped to the column…

Hello @John Carlo Pattaguan Welcome to the Atlassian community. Refer to the documentation on Pagination of results and the information there about the maxresults option: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#pagination

Yes, indeed, I was getting to that point eventually. ;-)