Petter Gonçalves Atlassian Team

You are welcome, @Dom Have a nice week and let us know if that automation worked as you expected.

You are welcome, @Vera Rabkina The site where a tested the automation above is a Jira Cloud site, so it might work in the same way for you. Have a nice weekend and let us know if you have any other questions.

Hello Etienne, I'm glad to know I was able to help you. Have a nice weekend!

Hello @Vera Rabkina You are welcome! Thank you for pointing out my mistake. Indeed, I have uploaded the wrong screenshot in my last reply. I edited it with the correct one now. Please, let me know if that automation works as you need.

Hello @rozmeen.khudabux Welcome to the Atlassian Community. Per your description, I understand the backlog of your Scrum board is only returning Epics and issues with no Epics, although the board filter is returning Stories assigned to Epics too. Please, check the following steps to troubleshoot the possible reasons for…

Hello @Fernando Montes Thank you for reaching out. The REST API syntax must have the "&&" parameter to properly search for multiple users, so this would be the correct endpoint: rest/api/3/user/email/bulk?accountId={accountId}&&accountId={accountId} Additionally, as you can see in the official REST API documentation, the…

Hello @Todd Thelin Thank you for reaching out. I'm not sure if I completely understood your request, but it seems you are looking for an automation rule to properly copy the assignee from parent to child issues when creating the child-issue. Is that correct? Also, when you say "Child-issues", I believe you are talking…

Hello @Kimberly Kriegler Just like @[deleted] mentioned, you will not lose any issues/Stories if you delete a Sprint, so you can simply create another Sprint, move the issues to the new created Sprint and delete the old Sprint. Additional to that, if you have a big amount of issues that would take too much time to manually…

Hello @Vera Rabkina Welcome to the Atlassian Community! Per your description, I understand you would like to automatically add the older unreleased version to your issues when you transition them to the "Closed" status. Is that correct? You can achieve this goal using the Jira Automation functionality. These would be the…

Hello @Ashley Massa Welcome to the Atlassian Community! I'm sorry, but I believe there are some misunderstandings in your question description that could be causing the unexpected behavior you are facing, so please allow me to provide you with some concepts so we can confirm we are in the same page here: You mentioned that…

Hello @Etienne Gautier Sorry to see you are facing a problem to complete/delete a Sprint. Please, allow me to provide you with some concepts and ask some questions so we can better troubleshoot the problem and confirm we are on the same page: As you may know, a board/Sprint can be configured with issues from multiple…

Hello @Narendra Kumar Thank you for reaching out. Per your description, I understand that you are looking for a rest API point that provides if a specific user is active or not. Is that correct? The default REST API to search for users provide you with the active parameter, which can have the following values: * True = The…

Hello @Zaldy Parian Thank you for reaching out. I hope you are safe and well too! Per your description, it seems you are trying to import sub-tasks to your Jira from an external source (CSV or JSON), however, you are not being able to map them as sub-tasks. Is that correct? Can you please confirm what are the steps and…

Hello @Tom Lister Thank you for reaching out. Indeed, users added as watchers were not getting notified with the "Mentioned you" notification that is usually sent when mentioning a user, however, we got some good news for you: As you can see in the feature request below, we changed the way that the mention notification…

Hello @Catherine Kong Thank you for reaching out. Basically, an Atlassian Organization is a centralized feature where you can manage all your users in a single place, even if they are using different sites or products. That being said, these would be the abilities of each role: Organization Admin: Can manage the whole…

Hello @Giovanna Berry Welcome to the Atlassian Community! When you say that you want to restrict the issues in the roadmap only to the relevant users, are you meaning the Roadmap feature of a Next-gen Project? Or are you talking about another feature from a Classic project? You can easily restrict specific issues of a…

Hello @Dom Per your description, I understand you would like to automatically create a link between issues under the same Epic. This goal can be easily achieved by automation for Jira, however, you will need to define a trigger for this operation. Let me give you a practical example: Let's suppose you want to link all the…

Hello @Pétur Björn Thank you for reaching out. Per your description, I understand that when someone forwards an e-mail to your Service desk about a pre-existing issue, a new issue is created instead of adding a comment to the original one. Is that correct? Or the two issues are being created at the same time when you…

Hello @Pétur Björn Thank you for reaching out. Per your description, I understand that you would like to set a single component when an issue is created through E-mail in your Jira site. Is that correct? You can do it by using Automation rules. These would be the steps: * Navigate to your project > Project settings >…

You are welcome, @Emily Uberti Have a nice day!

Hello @Juliana Miranda Can you confirm if you are still facing this problem in your Jira Service desk? Per your screenshots and the details of the problem, the issue should properly be solved after the option mentioned by @Thorsten Letschert _Decadis AG_ is flagged. If that did not work for you, I suggest double-checking…

Hello @Van Kieu To make a request type compatible when moving issues, the Issue-type must be mapped to it under project settings > Request type: Additionally, you can map issue types to request types in a different way from project to project, so you should always consider the issue type and request type mapped in the…

Hello @Yaitza_Luna-Cruz Thank you for reaching out. Jira has the functionality to set a field as required in an issue, so if the user keeps that field empty, a pop-up is prompted to fill that specific field before the issue is transitioned. Unfortunately, that functionality was not implemented for Next-gen yet, although we…

Hello @Peter Waring Thank you for reaching out. Unfortunately, it is not possible to edit the fields displayed in the cards of Next-gen boards. We understand how this functionality would be useful, so we created the following feature request to get it implemented: Ability to customize the fields shown on cards in next-gen…

Hello @sven.dillmann Thank you for reaching out. Per your description, I understand you would like to use a JQL query to return the Epics related to Stories that are configured with a specific Version. Unfortunately, this type of "Sub-query" is not supported in the Jira application. We understand how useful this feature…

Hello @Laura Pilath Welcome to the Atlassian Community! Per your description, I understand you are not being able to add fields to issues and create versions in your projects. Please, allow me to ask you some questions and provide you with some concepts so we can better confirm we are on the same page: Can you confirm if…

Hello @Emily Uberti Welcome to the Atlassian Community! I understand you would like to display the time that an issue was added to a specific Component in your Jira. It is possible to visualize the dates that the component was added and remove in the history of the issue, however, Jira does not have a field that would…

You are welcome @pierre_gendre Have a nice day!

You are welcome, @KPrice Have a nice day! :)

Hello @Anand_G Welcome to the Atlassian Community. Sorry to see that you are facing some problems when linking issues through the CSV import. Per your description, it seems you are trying to link tasks to Stories using the parent ID Column. If that's the case, I believe you might be misunderstanding how the issue link…